It isn’t that it is a known issue and will be resolved soon.
It is because the webrep no longer supports bleeding edge versions, e.g. alpha, beta, nightly or whatever names are flying about for non-regular release versions and this is for firefox also.
Chrome v18 ATM is the Beta Channel.
Chrome Beta updates quite frequently.
And there were a few versions of Chrome Beta last summer where WebRep v6 didn’t work either.
So this isn’t entirely a new issue with Avast 7
More glaring a Chrome issue is how Avast is offering or auto installing Chrome on PCs that already have Chrome. But Avast is installing the enterprise** Stable Channel flavor that puts Chrome in the Program Files directory.
The user then ends up with two Chrome installs which screws up the Chrome user profiles.
**I am a Google Apps Administrator and can tell you that us domain managers have the option of obtaining an enterprise version of Chrome that installs in the Program Files directory.
I feel reasonably confident this is also the version that Avast is pushing out.
To be complete-
Chrome has 3 main flavors, Stable, Beta, and Dev
All are available for public download (release)
There is also an enterprise version not so easily accessed by the public.
The enterprise version is the Stable Channel but made for network installations and ends up placing Chrome in the Program Files directory. (It may be that this is what Avast is offering during install)
But technically the Beta Channel is beta
and as of today
Stable is v17
Beta is v18