1503095 - ALT key in macOS

Status: RESOLVED INCOMPLETE

(Firefox :: Sync, defect, P3)

Description

[iliketoeatwheat]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.102 Safari/537.36 Vivaldi/2.0.1309.42

Steps to reproduce:

Pressing the option key on macOS isn't recognized as pressing the alt key.

Can test here: http://www.keyboardtester.com/tester.html


Actual results:

Commands on some webpages involving the alt key don't work on macOS.


Expected results:

Pressing the option key should map to the alt key. (Works on chromium browsers). There doesn't seem to be a way to simulate pressing just the alt key on macOS.

Comment 1

[Stephen A Pohl [:spohl]]

This works properly for me in Firefox 63. What version does this reproduce in for you? Is this specific to macOS 10.14?

Comment 2

[iliketoeatwheat]

(In reply to Stephen A Pohl [:spohl] from comment #1)
> This works properly for me in Firefox 63. What version does this reproduce
> in for you? Is this specific to macOS 10.14?

Testing in Firefox 63.0.1. I tested the issue some more, and it seems that the issue is caused by my Firefox sync account or possibly the about:config page. Reinstalling Firefox and deleting all settings fixes the issue, but signing in causes the alt key to break again. Signing out of the Firefox account and "deleting user preferences" doesn't fix the issue, but I suspect this might be because the about:config page isn't wiped when signing out.

Comment 3

[Stephen A Pohl [:spohl]]

Adjusting component based on comment 2.

Comment 4

[Ryan Kelly [:rfkelly]]

Interesting, it certainly sounds like it's syncing down a bad config option or addon or something.  ni? :markh for some advice on how to debug this.

Comment 5

[Mark Hammond [:markh] [:mhammond]]

I can't think of anything that could cause this - we don't sync any preferences which could cause this (and I can't find evidence any such pref exists anywhere), and I don't think webextension addons could change this either.

Does this problem still exist?

Comment 6

[Mark Hammond [:markh] [:mhammond]]

Thanks again for reporting this issue, but we are unable to determine the cause of the problem without the requested information. If you are able to provide this information, please just add a comment in this bug with that information and we'll get back to you as soon as we can, but in the meantime we are closing this bug so we can focus on the issues which we can address.