Going by my experience, and what I have read so far, yes, I would feel much safer with IE or FF. What good is a web-shield if the browser is not gonna respect aborted connections?
The point is Randy you can be equally protected by adding some free and low to 0 resource security by way of K9 and ClearCloud DNS as well as an additional browser intergrated offering such as Norton Safe Web, this combined with WOT makes you very safe, but it seems Avast primarily is going to protect IE and FF which is not to say the other browsers do not get protection, just that I think with IE and FF having the most users the program(s) (Avast in this case) are more geared towards them.
The system requirements of avast! have never mentioned any particular browser, and nor has there been any official word on it.
The misbehaving app here is the browser - chrome/opera/safari. The onus of proper respect of an AVs attempt to abort the connection lies with the browser. The API is available to be made use of in all versions of Windows since XP SP2.
The fact that nobody from avast! is clearing this up is surprising. We need someone official and qualified to tell us in plain english if there is a difference in the way different browsers interact with avast’s web shield. If yes, then on whom does the responsibility of correcting it lies.
I totally agree Ravi, I just feel it is very likely due to the typical support for IE and FF that these are more supported if you will, I too though hope to see an answer from Avast that can clear up the question.
