Closed Bug 644868 Opened 13 years ago Closed 8 years ago

the entire browser is slow , partially unresponsive and is not compatible with mcafee site advisor

Categories

(Plugins Graveyard :: McAfee AV, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: jlul, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows NT 5.1; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0) Gecko/20100101 Firefox/4.0

although you folks deemed "sucks" a bad example, it fits. I have experienced nothing but negative impressions since I downloaded 4. Go back to the drawing board, as it really needs fixing. It is slow, partially unresponsive, partially ambiguous and is not compatible with mcafee site advisor. I believe that if I use it longer, I will really want to find another browser. Is there a way to go back to 3.6? Thanks for listening to my rant., Joe

Reproducible: Always
Bugzilla is not a support page for endusers, it's a tool for our developers.

You should try http://support.mozilla.com/en-US/kb/Safe+Mode first.

I requested to block the old site advisor extension because it broke Firefox. A new Version is AFAIK available on the mcafee homepage.

use http://www.mozilla.com/en-US/firefox/all-older.html for older versions
Version: unspecified → 4.0 Branch
We're now tracking such bugs. This doesn't mean it's something we can fix, merely something we hope to be able to point vendors to so they can investigate. This is an automated message.
Component: General → McAfee AV
Product: Firefox → Plugins
QA Contact: general → mcafee-antivirus
Version: 4.0 Branch → unspecified
Depends on: 637542
Closing old bugs in the Plugins component. We aren't going to track issues in 3rd-party plugins in the Mozilla bug tracker. In addition, support for NPAPI plugins will be removed at the end of this year; for more details see the post at https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/

If there is a serious bug in Firefox, it needs to be filed in the "Core" product, "Plug-Ins" component.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Product: Plugins → Plugins Graveyard
You need to log in before you can comment on or make changes to this bug.