My question, which I have not had answered is about the status of this. If you had looked at the link I gave you will see the extent of the mess it creates on the page.
I wanted support, or someone knowledgeable to:
1 Confirm that what I am reproducing is correct. It could well be I am doing something silly and I would like to know if that is the case.
2 Tell me how I can turn this feature off. The software is very detailed and complex now and it is easy to miss options.
3 Tell me that this is indeed a fault and will be corrected with an option to switch off, at the next release, if that is the case.
4 Tell me that is is a non-optional feature that is part and parcel of the new avast product and if I don't like it tough luck.
That's all. It would take the support here less than a minute to respond I would think.
1/ I cannot see any mess on that page anywhere. And for that matter, nor can I see any ticks, or boxes, or whatever Avast-related there. Tested with IE and Chrome. Don't have FF installed.
2/ No such settings as far as I can tell. Then again, the normal behaviour is shown on the screenshot in
this post. You get the ticks right to links on certain pages (such as search engines) and
only when you hover that with your mouse cursor, you get your "intrusive" box.
3/ The only action I get from the browser extension on the Stack Overflow page is blocking a bunch of social/tracking junk./ So, all in all, if what you are reporting is that you
get some green boxes without any interaction with the page, then it's most likely Firefox-specific cosmetic issue.
4/ The browser extension is entirely optional.
Finally, if you consider those "intrusive", check things like WOT, the hover infoboxes are whole lot more "intrusive".
That's all. It would take the support here less than a minute to respond I would think.
If you want support to respond, that's what support tickets are for. There's no reply guaranteed anywhere on this forum, though Avast staff reads and responds quite often here. You need to consider, however, that this is a cosmetic browser specific issue worst case, so realistically extremely low priority for any development purposes.
