Closed
Bug 434260
Opened 16 years ago
Closed 16 years ago
Firefox is very slow on some pages with custom mouse events (MUCH slower than other browsers).
Categories
(Firefox :: General, defect)
Tracking
()
People
(Reporter: sambucus-general, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.9) Gecko/2008051206 Firefox/3.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.9) Gecko/2008051206 Firefox/3.0 Firefox is very, very slow on some pages with custom mouse events - MUCH MUCH slower than IE, Opera and Safari, to the point where term "FPS" applies. Specifically, applies to vertical page scrolling. CPU usage rises enormously then, too. My friend, a web developer, after having a quick look at one of the pages, said this: "They overwrite/replace onMouseScroll event in some weird way. Probably hook the 2D click map counting script up with it." I'm not a web developer myself, so please excuse me if the translation is not that great - I have no idea what this actually means. :) IE is much much much faster, the same for all the other browsers I mention above. The supplied URL demonstrates the problem. It's been there in Fx 2, also. Reproducible: Always Steps to Reproduce: 1. Visit the specific page, with which other browsers have absolutely no problems. 2. Scroll the page vertically. Actual Results: Extremely slow page scrolling with CPU usage at 100% (50% on a dual-core machine). Expected Results: I'd like to see normal vertical scrolling, where "frames per second" does not apply and the CPU usage remains around 0%. :) Happens with Fx3 default theme and all the add-ons disabled, too. Was also present in Fx 2.
Comment 1•16 years ago
|
||
It's slow also on Linux. Adding the following rule in userContent.css makes the performance much better... @-moz-document url-prefix(http://gamecorner.pl/gamecorner/) { body { background-image:none!important; } }
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•16 years ago
|
||
@ Mats Palmgren: Thank you for the suggested solution, I'll definitely try it. So, it's a result of something else, after all. Good to see it reported, too bad it isn't fixed yet. :(
You need to log in
before you can comment on or make changes to this bug.
Description
•