Closed Bug 1401837 Opened 7 years ago Closed 7 years ago

Navigation buttons (forward/backward) on mouse no longer function on upgrade from 56.0b12 to 57.0b1 on macOS

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

57 Branch
x86_64
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1399086
Tracking Status
firefox-esr52 --- unaffected
firefox55 --- unaffected
firefox56 --- unaffected
firefox57 --- fixed
firefox58 --- fixed

People

(Reporter: nermolov1, Unassigned)

References

Details

(Keywords: regression)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:57.0) Gecko/20100101 Firefox/57.0 Build ID: 20170917031738 Steps to reproduce: 1) Install FF aurora 57.0b1 on macOS 2) Open a new page and navigate through a link to allow navigation backward 3) Press back button on compatible mouse (this was tested with the Logitech MX Master with the official Logitech Options drivers - latest version at time of posting) Actual results: Nothing occurred. Expected results: The tab should have navigated backward one step in history as it did in 56.0b12. I have verified that this is not an issue with mouse drivers as this issue is not present in other applications - notably Google Chrome.
Can confirm on 57.0a1 (2017-09-21) (64-bit) Regular Firefox works as expected on my machine.
Keywords: regression
OS: Unspecified → Mac OS X
Hardware: Unspecified → x86_64
Moving to the correct component. See also Bug 1399086.
Component: Untriaged → Event Handling
Product: Firefox → Core
Flags: needinfo?(spohl.mozilla.bugs)
Flags: needinfo?(mstange)
Flags: needinfo?(spohl.mozilla.bugs)
Flags: needinfo?(mstange)
Hi Nermolov1, I've did some diggings and found out that back and forward mouse buttons are not supported by default on Mac OS. You either need a software for this or the mouse manufacturer must support them through drivers. Please verify if you have the latest driver version for the Logitech MX Master mouse installed (6.70.1197 - http://support.logitech.com/en_us/product/mx-master/downloads#). If you have the latest driver, is there a chance to have an older one to verify if this issue is also reproducible with it? If both the new and old drivers are manifesting the issue, could you please try to install one of Mozilla's tools wich could help us find the issue that generated this behavior. We don't have a mouse from Logitech to try and reproduce this on our end, so you could help us if you have a bit of time. You can install Mozregression tool from the next link http://mozilla.github.io/mozregression/install.html. Just use the terminal commands mentioned in the tutorial and after use the next command (without commas) to start testing: "mozregression --good 2017-06-12 --bad 2017-09-21" When a Firefox window is opened try to reproduce the issue. If the issue is reproducible write "bad" in the terminal and hit "Enter", if is good write "good". Please provide us the pushlog link after no more builds are opened by the tool.
Flags: needinfo?(nermolov1)
Confirmed with older versions of logitech drivers. I ran mozregression and got the following last pushlog link: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=a85670ee5e959299556b6ad0ef1370743debc43d&tochange=8a67124d36d9ed0c6fa9111ae33620aeddc4ce4d The entire mozregression console output is here: https://gist.github.com/nermolov/7548ce300b25c965017e0602c55ba570
Flags: needinfo?(nermolov1)
That feels similar or dupe of my bug 1399086. But not sure how the Logitech driver implements the buttons.
What versions of macOS does this reproduce on? Is 10.11 from comment 0 a system that reproduces this? What about 10.12 and 10.13?
Flags: needinfo?(nermolov1)
Status: UNCONFIRMED → NEW
Ever confirmed: true
22:21.20 INFO: No more inbound revisions, bisection finished. 22:21.20 INFO: Last good revision: a85670ee5e959299556b6ad0ef1370743debc43d 22:21.20 INFO: First bad revision: 8a67124d36d9ed0c6fa9111ae33620aeddc4ce4d 22:21.20 INFO: Pushlog: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=a85670ee5e959299556b6ad0ef1370743debc43d&tochange=8a67124d36d9ed0c6fa9111ae33620aeddc4ce4d
I'm on OSX Sierra - 10.12.6 (16G29)
Looks as if the changeset in Comment 7 points to Bug 1324892, which is the bug where we changed the SDK.
I'm on El Capitan - 10.11 I cannot upgrade to 10.12 due to some hardware issues.
Flags: needinfo?(nermolov1)
I was able to track this down and can confirm that this is the same issue as in bug 1399086. Taking fix and discussion over there.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.