Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

error reporting in the 'Developers Toolbar' (shift + F2) is logging every event as an error

  • 3 uphendule
  • 7 zinale nkinga
  • 7 views
  • Igcine ukuphendulwa ngu user1929

more options

All events (image load, click, etc) gets reported as an error in my Developers Toolbar (shift + F2). Tried multiple websites, multiple tabs, reboot and even a different computer. Anyone know how to fix this?

All events (image load, click, etc) gets reported as an error in my Developers Toolbar (shift + F2). Tried multiple websites, multiple tabs, reboot and even a different computer. Anyone know how to fix this?
Ama-screenshot ananyekiwe

Okulungisiwe ngu mdenhartog

All Replies (3)

more options
more options

Thanks for your reply! Disabling the 'multi process support' doesn't sound like an ideal solution for a bug in a out-of-the-box plugin.

I also agree with the feedback of the owner of the question in the link you suggested;

"However, I certainly would prefer Firefox to be as fast and secure as it can be. Disabling multi-process support doesn't sound ideal, though it does stop the error count from going haywire.

Also, I do use the console in the developer toolbox. But I like how the toolbar alerts me to errors even if the console is not open. That way, I don't have to browse with the console always open."

Would be awesome if Mozilla could fix the problem in an upcoming release :)

more options

Yeah, I would agree. If you go the Bugzilla page, you can vote for the bug, but based on the comments there I doubt this is going to be fixed anytime soon.