Closed
Bug 1303903
Opened 8 years ago
Closed 8 years ago
No longer fire DOMMouseScroll event on browser while the | menupopup, panel | is displayed
Categories
(Core :: Widget, defect, P3)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: alice0775, Unassigned)
References
Details
(Keywords: addon-compat, regression, Whiteboard: tpi:+)
my addon[1] stops working after landing bug 982121. [1] https://addons.mozilla.org/en-US/firefox/addon/bug643770stop-autoscroll-by Steps to Reproduce: 0. Enable chrome debug. i.e. devtools.chrome.enabled=true 1. Open Browser Console and Scratchpad 2. Run the following code as browser code window.addEventListener("DOMMouseScroll", function(event) { console.log("DOMMouseScroll"); }, true); 3. Open any popup such as menupopup, contextmenu, autoscroll marker 4. Turn mouse wheel on browser (not on the popup) Actual Results: The wheel event does not fire Expected Results: The wheel event should fire Regression window: https://hg.mozilla.org/integration/fx-team/pushloghtml?fromchange=c6e90a3857c019e418c113f31dec86ca43e60243&tochange=4cab5471b2fa42dd7d0560f8f35dcc4e82a9414e Regressed by: 4cab5471b2fa Gijs Kruitbosch — Bug 982121 - consume wheel events when popups are open, r=enndeakin
Reporter | ||
Updated•8 years ago
|
tracking-firefox52:
--- → ?
Comment 1•8 years ago
|
||
Expected behavior from the work in bug 982121?
Flags: needinfo?(gijskruitbosch+bugs)
Whiteboard: tpi:?
Comment 2•8 years ago
|
||
(In reply to Jim Mathies [:jimm] from comment #1) > Expected behavior from the work in bug 982121? I think so. Doublechecking with Neil.
Flags: needinfo?(gijskruitbosch+bugs) → needinfo?(enndeakin)
Comment 3•8 years ago
|
||
Yes, this would be expected.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(enndeakin)
Resolution: --- → INVALID
Reporter | ||
Comment 4•8 years ago
|
||
I do not agree. I think this is just unexpected side effect of bug 982121. And I can agree that the event does not fire if it is bubbling phase. However, The event should fire, because the listener is attached to the top most browser element and capturing phase. And this is braking addon. There are no workaround.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Reporter | ||
Comment 5•8 years ago
|
||
I suggest that bug 982121 should be backed out.
Comment 6•8 years ago
|
||
We should instead just fix 213496/643770 (which are duplicates, I think)
Updated•8 years ago
|
Comment 8•8 years ago
|
||
Neil clarified for me that what he meant by comment 6 was that fixing bug 213496 (or the potential-dupe bug 643770), we would obviate the need for the addon that got broken but the change in bug 982121. Neil said he'd take a look at how hard it would be to fix bug 213496 (or bug 643770) so I'll set needinfo here to keep it in his queue. Thanks, Neil.
Flags: needinfo?(enndeakin)
Comment 9•8 years ago
|
||
The patch in bug 643770 will fix the underlying bug the addon was created for. The addon could just add rolluponmousewheel to the popup as well as the patch there does and have this work in current releases, and has the benefit that it will work on Mac and Linux as well, which the addon doesn't handle as far as I can tell.
Status: REOPENED → RESOLVED
Closed: 8 years ago → 8 years ago
Flags: needinfo?(enndeakin)
Resolution: --- → WONTFIX
Reporter | ||
Comment 10•8 years ago
|
||
(In reply to Neil Deakin from comment #9) > The patch in bug 643770 will fix the underlying bug the addon was created > for. The addon could just add rolluponmousewheel to the popup as well as the > patch there does and have this work in current releases, and has the benefit > that it will work on Mac and Linux as well, which the addon doesn't handle > as far as I can tell. What about the event capture phase and it is targeted root window . The event is no longer fired. I do not understand why?
You need to log in
before you can comment on or make changes to this bug.
Description
•