Closed
Bug 235965
Opened 20 years ago
Closed 19 years ago
mouse wheel stops working after a few clicks
Categories
(Core Graveyard :: GFX: Gtk, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: dicks, Assigned: blizzard)
References
()
Details
Attachments
(1 file)
424 bytes,
text/html
|
Details |
User-Agent: Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040225 Firefox/0.8 Scrolling the page at the URL mentioned above with the mouse wheel stops after a few clicks. Scrolling with the arrow keys or scroll bar still works. After Page-Up, the mouse wheel works again, but for a few clicks only. This is a regression in Firefox-0.8. The page works fine with Firebird-0.7 (Gecko/20031225). Reproducible: Always Steps to Reproduce: 1. Visit the URL http://www.rtl.nl/actueel/rtlnieuws/ 2. scroll down a few clicks using the mouse wheel 3. Actual Results: The mouse wheel stops working. Expected Results: The mouse wheel should not stop working (duh!).
WFM LInux Mozilla 2004032308 I see it on LInux Mozilla week old CVS build w/gtk2/xft I see it on LInux FF 20040323 w/GTK2/xft WFM LInux FF 20040323 w/gtk1
Assignee: events → blizzard
Component: Event Handling → GFX: Gtk
Assignee | ||
Comment 2•20 years ago
|
||
Interesting. Looks like all the scroll events are being delivered to one of the menus on the left. Not sure if that's intentional or not. The widget system certainly is delivering them so this doesn't appear to be down at the widget layer. Probably something higher in the view manager or dom?
Hrr. Jesiah, can you narrow down the regression further?
Using Mozilla CVS I narrowed it down to 15-17 Sep 2003 00:00 PST. This seems odd as Firebird 7's modified dates on the servers are Oct 15. Note: that after and including the 17th this bug will only show up in certin places but not the whole screen like more current versions of mozilla. When you move the mouse a few inches it will start scrolling again.
Jesiah, THANKS!! I suspect bug 69355. Jesiah, can you try producing a small testcase? I suspect it involves the use of "overflow:hidden". One thing to try would be removing all overflow:hidden from the test page(s) you already have and see if that makes the bug go away.
okay, I'm pretty sure this is overflow:hidden elements eating the scroll events (because they're now a special case of scrollable elements). But I can't easily see exactly what's going on here because I don't have a wheel mouse. Maybe David can help...
Comment 8•19 years ago
|
||
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/
Comment 9•19 years ago
|
||
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
Updated•16 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•