Closed Bug 435591 Opened 18 years ago Closed 18 years ago

Scolling the page causes the browser to stutter

Categories

(Firefox :: General, defect)

PowerPC
macOS
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: vijay.kantavil, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9) Gecko/2008051202 Firefox/3.0 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9) Gecko/2008051202 Firefox/3.0 The scrolling on this webpage becomes very laggy and I thought it was the webpage problem but upon testing it on Safari, it works just fine. Reproducible: Always Steps to Reproduce: 1.Go the http://uk.playstation.com/games-media/news/articles/detail/item104026/Siren-Blood-Curse/ 2.Scroll the page 3. Actual Results: Page lags Expected Results: Smoothing scrolling
I'm not able to reproduce this. I saw no lags scrolling this bug's page in Firefox 3 RC 1 on OS X 10.5.2 (on a recent MacPro).
That's funny, as I am still having the issue. I am using a Macbook 2.2Ghz with the release candidate one as well. I doubt the issue is anything other then Firefox related as I am able to browse the site on Safari flawlessly.
I don't disbelieve you. But nothing can be done about this until some developer (like me) can reproduce it. Later I'll test again on an old MacBook Pro.
Thanks
I've now tested on my early model MacBook Pro (2 GHz Intel Core Duo), in both OS X 10.5.2 and 10.4.11. I didn't see any lags. So I'm going to mark this WORKSFORME. It may be that I'm missing crucial information, or that the effect is very subtle. But in either case I don't (currently) have anything to work with. Please reopen if/when you find precise, detailed steps to reproduce a _very_ noticeable bad effect.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
I can reproduce it - it's caused by about 13 flash objects. When the page has loaded, every navigation button and every headline is replaced by a flash box. In Safari, this doesn't happen, but I haven't been able to find out why - the script doing it (mikr.js) is executed in Safari, too.
You need to log in before you can comment on or make changes to this bug.