> it looks to me as if you're trying to convince > everyone that there isn't any bug. I do not see a bug. I can not reproduce the problem when using a trunk build on windows. I can not reproduce the problem when trying all of the mentioned URLs so far, including this bug's provided URL http://www.w3.org/Style/Examples/007/scrollbars.html and attachment #139911 . Now, if the bug is still happening on the trunk, then provide a testcase relevant and relative to this bug. Do you understand? I am trying to convince you that several of the so-called URLs, testcases included in this bug were - 404 not found - redirected to nowhere - abusing or depending on Flash - abusing or depending on javascript - have huge amount of coding errors, are examples of over-excessive formating, over-excessive coding, declaring, over-constrained layout, - etc.. and that none of this serve the purpose of demontrating or reproducing or isolating a bug or faulty behavior or weak performance. If this bug still occurs, then at least a large minority of us should notice, measure something significant when trying attachment attachment #139911 or this bug's provided URL. > I do think there's is something with this > position:fixed Fine! Then proceed accordingly with What is a Simplified Test Case, and How Do I Make One? http://www.mozilla.org/newlayout/bugathon.html#testcase How to Really, Really Help Developers on Bugs -- Minimal Testcases http://wiki.mozilla.org/MozillaQualityAssurance:Triage#How_to_Really.2C_Really_Help_Developers_on_Bugs_--_Minimal_Testcases There are such things as the capability to reproduce a bug under controlled conditions, where we can compare data, examine testcases, use and compare (before fix and after fix) performance profiles, etc... Otherwise we shouldn't confirm a bug. > I wasn't comparing smoothscroll. Why do people in this bug keep mentioning smooth scroll then? Why can't you provide smooth scroll related data to respective bugs like bug 202718 (Windows), bug 424308 (Mac), bug 409456 (Linux)? > Here are the results again, with smoothscroll off: > FF2: between 3 and 5 seconds, redrawing maybe 4 or 5 times a second > FF3: between 13 and 15 seconds, redraw once a second > that's 4 to 5 times slower. Which test case are you referring to? What's your overall system configuration for getting those data? I can not reproduce anything close to your data with this bug's provided URL http://www.w3.org/Style/Examples/007/scrollbars.html and attachment #139911. > I've posted an attachment already a few weeks ago, cleaned up from all the > images only but not css. I know I should have created a simple file with a > fixed div and some text... I did read the 'howto' file a bug and do tests, > etc... > > But in my case it's a bit complex. It is **NOT** just a bit complex. It's an 85 Kilo-byte HTML file (7598 lines of code, 86193 bytes!) with several linked (external and imported) stylesheets and several linked external javascript files that we can not see or examine with your RAR compressed file because your very long HTML file uses relative addressing, not absolute addressing. And I'm not even mentioning inline style, inline javascript code, invalid markup code, for populating dynamically "n" tables and table cells, etc..: