alt+wheel mouse move in history and conflict with XFCE accessibility
Categories
(Core :: DOM: Navigation, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox81 | --- | wontfix |
firefox82 | --- | wontfix |
firefox83 | --- | verified |
People
(Reporter: popolon, Assigned: johannh)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(1 file)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0
Steps to reproduce:
In a firefox beta 80, window, and I stroke alt+mouse wheel.
Actual results:
The current page is moving very fast in the history (and an unusable way), that was not the case in previous version, conflicting with accessibilty
Expected results:
Nothing, this conflict with alt + wheel mouse accessibility zoom in XFCE window manager.
Sorry this bug is in firefox 81 beta, not 80 (stable I use here).
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Comment 2•4 years ago
|
||
I can reproduce the issue on Nightly83.0a1 Windows10.
Steps to reproduce:
- Open new tab
- visit https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions from address bar
- visit https://ftp.mozilla.org/pub/firefox/nightly/ from address bar
- visit https://en.wikipedia.org/wiki/Wikipedia from address bar
- Alt+mouse wheel down / up
Actual results:
The tab history of step 2,3 are skipped
Expected results:
The tab history should be back and forward in sequence.
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=87ad6cc2ae3f5af22335f8a1c3213a14f990fc50&tochange=891bf9d395fd25e5dee20f67278a591d7dd47e84
Assignee | ||
Comment 3•4 years ago
|
||
That's strange because browser.navigation.requireUserInteraction
is set to false at the moment. So entries shouldn't be skipped. What's the value of that pref for you?
If it's true
then it's a dupe of bug 1644914.
Assignee | ||
Updated•4 years ago
|
Comment 4•4 years ago
|
||
The bad build(79.0a1) of the regression window:
browser.navigation.requireUserInteraction=true
82.0b8 and 83.0a3(reproducible the issue):
browser.navigation.requireUserInteraction=false
Assignee | ||
Comment 5•4 years ago
|
||
Ok, thanks, I'll take a look.
Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
Comment 6•4 years ago
|
||
Severity N/A because this bug doesn't currently affect users because requireUserInteraction is off by default.
block requireUserInteraction meta bug 1645211
Assignee | ||
Comment 7•4 years ago
|
||
This is incorrect, the pref doesn't seem to matter here according to comment 4.
Personaly I had this only on 81 beta, not in 80 stable, 81 stable and 82 beta is not affected either.
Assignee | ||
Comment 9•4 years ago
|
||
Can you confirm that this is caused by flipping the browser.navigation.requireUserInteraction
to true
? Thanks!
Comment 10•4 years ago
•
|
||
The problem is
https://searchfox.org/mozilla-central/source/dom/events/EventStateManager.cpp#2319
requireUserInteraction seems to be always true when calling webNav->GoBack(GoForward), so we hit the underlying bug like bug 1644914.
Reporter | ||
Comment 11•4 years ago
|
||
browser.navigation.requireUserInteraction is false on both 81 and 82b, and I didn't changed it.
Updated•4 years ago
|
Assignee | ||
Comment 12•4 years ago
|
||
Comment 13•4 years ago
|
||
Comment 14•4 years ago
|
||
bugherder |
Updated•4 years ago
|
Comment 15•4 years ago
|
||
Reproduced the issue on affected Nightly83.0a1 on Windows 10 x64.
Verified-fixed on latest Nightly 84.0a1 (2020-10-21) (64-bit) and Beta 83.0b2 on Windows 10 and Ubuntu 16.04.
Description
•