Open
Bug 1333214
Opened 8 years ago
Updated 2 years ago
Container properties: accesskeys don't work under macOS
Categories
(Firefox :: Settings UI, defect, P5)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox54 | --- | affected |
firefox57 | --- | fix-optional |
People
(Reporter: kjozwiak, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [userContextId][domsecurity-backlog])
In bug#1326087, we fixed the access key for container properties under about:preferences#containers. However, it seems like the shortcuts are not working as expected under macOS. Rather than selecting the correct item, macOS inserts accent characters under "Name". The only way I managed to get the shortcuts to work was when "Name" is not being selected.
STR:
* visit about:preferences#containers
* select "Preferences" on a random container
* attempt using the shortcuts that should be working under macOS [1]
> control + alt (option) + n
> control + alt (option) + o
> control + alt (option) + i
* macOS will type in accent codes into the "Name" field rather than using the appropriate shortcut
Now, you can get the shortcuts working with the following:
* press alt (option) + command + c which will launch the dev tools and unselect the "Name" field
* close the dev tools and you'll notice that the "Name" field isn't selected anymore
* you can now used control + alt (option) + o & control + alt (option) + i as long as you don't go back into the "Name" field
[1] http://searchfox.org/mozilla-central/source/browser/locales/en-US/chrome/browser/preferences/containers.dtd
Reporter | ||
Comment 1•8 years ago
|
||
As pointed out by Mihai in bug#1326087comment#13, the "Name:" field appears to always be selected under macOS, hence the keyboard shortcuts adding accent characters into the Name field.
Reporter | ||
Updated•8 years ago
|
Priority: P3 → P5
Comment 2•7 years ago
|
||
Bulk change per https://bugzilla.mozilla.org/show_bug.cgi?id=1401020
status-firefox57:
--- → fix-optional
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•