Closed
Bug 1275657
Opened 8 years ago
Closed 8 years ago
Arrowscrollbox processes PageUp/PageDown mouse wheel events incorrectly.
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1251987
People
(Reporter: estart, Unassigned, NeedInfo)
Details
+++ This bug was initially created as a clone of Bug #1272991 +++ User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:46.0) Gecko/20100101 Firefox/46.0 Build ID: 20160502172042 Steps to reproduce: 1) Set mouse scroll in windows control panel to "one screen at a time". 2) Open the bookmarks popup menu (or any other arrowscrollbox list) in the main menu. Bookmarks must be a sufficient number (e.g. 100). 3) Make one scroll the mouse wheel down or up. Actual results: It will scroll to the beginning(top) or end(bottom) of the list. Expected results: Scroll one page up or down.
"I've tested again, and I realize that the element type <arrowscrollbox> is the criminal who don't respect "one page scroll" feature. http://mxr.mozilla.org/mozilla-central/source/toolkit/content/widgets/scrollbox.xml#469 http://mxr.mozilla.org/mozilla-central/source/toolkit/content/widgets/scrollbox.xml#303 When you move the wheel, DOMMouseScroll event is fired. The event has a property named "detail", and the value indicates how many lines we should scroll in the box. On <tree> or <listbox>, "event.detail" says correct value. However, on an <arrowscrollbox> element, when I set "mousewheel.withnokey.action" to "1", then "event.datail" is "2" on my environment. After I set "mousewheel.enable_pixel_scrolling" to "false", then "event.datail" is "32768" (equals to 215 - this is quite odd!) Both values are wrongly generated by Firefox itself. Similar issues: https://bugzilla.mozilla.org/show_bug.cgi?id=543338 https://bugzilla.mozilla.org/show_bug.cgi?id=723132 Now I'm reserching why the "event.detail" became an invalid value "32768"". - quote from here: https://github.com/piroor/treestyletab/issues/262#issuecomment-5505560
@ Dook (reporter): I suppose you reported it again because bug 1251980 was closed as Duplicate of bug 1251987, which in turn was marked as Fixed... If that's the case, read the explanation below. Otherwise please name your reason. Well, the thing is bugs are marked as Fixed when they are fixed in the latest alpha version of browser. So bugs marked as Fixed may be present on release version. I haven't checked it earlier, but bug 1251980 was fixed by bug 1251987; my apologies. You can download + install the latest alpha version to make sure the issue is resolved. Or, if you don't want to waste time, leave this bug open until fixes from bug 1263975 and bug 1251987 reach release version (~70 days). Here's the link of the latest alpha (Firefox Nightly): https://nightly.mozilla.org/
Flags: needinfo?(estart)
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•