Closed Bug 276093 Opened 20 years ago Closed 19 years ago

Slow form widget rendering - delays when depressing buttons, opening listboxes

Categories

(Firefox :: Shell Integration, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: turtle246, Assigned: bugs)

References

()

Details

(Keywords: perf)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Widgets on some forms (see example url) render slow. There is noticeable delay when you open a listbox, depress a button, or click & drag the scrollbar in an opened listbox (only delays just after a click; is fast in dragging thereafter until you re-click). It is interesting to note that when I start Macromedia Dreamweaver MX (whether before or after I start Firefox), the widgets on that page render fast. When I close Dreamweaver, they revert to slow. Another site with forms that act similarly: http://www.newegg.com Sites with fast widgets include: any vBulletin forum forms any phpBB forum forms amazon.com google Google Translations (which uses unicode like babelfish) pricegrabber.com It seems this shows up on very few websites. I'll post more as I notice them. It took me a while to find a second site (newegg) that had the same issue. Reproducible: Always Steps to Reproduce: 1. Open Firefox 2. Go to example sites 3. Click on form widgets 4. Try opening a language listbox, then click and quickly drag the scrollbar. Actual Results: Slow widgets, hang/delay (I'd guess 150ms) when depressing buttons or opening listboxes, and when scrolling in the listbox (only delays just after clicking the scrollbar). The scrolling in the listbox delays, then jumps to your position. Expected Results: Widgets should render as fast as any other standard Windows widgets.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.