Keyboard focus of links not working on Mac
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P3)
Tracking
()
People
(Reporter: hassan, Unassigned)
References
Details
(Keywords: regression, regressionwindow-wanted)
I'm not able to navigate links using the keyboard in Firefox. I was able to find a workaround by setting accessibility.tabfocus to 7 in about:config[1]. Is there a reason tab focus is disabled by default? Any clarifications would be appreciated.
|
||
Updated•5 years ago
|
|
||
Comment 1•5 years ago
|
||
This is expected behavior on MacOS, given it is the platform convention.
I don't have Safari to test right now, but IIRC it at least used to have similar behavior.
Marking invalid, but Neil may have more to say about this.
|
|
||
Comment 2•5 years ago
|
||
Safari has the same behavior as we do.
|
Reporter | |
Comment 3•5 years ago
|
||
It works on Chrome.
|
|
||
Updated•5 years ago
|
|
||
Comment 8•5 years ago
|
||
In MAC the tab-navigation behavior depends on the OS Keyboard setting.
Enabling "Full Keyboard Access" in the Keyboard preference would make link tab navigable.
Note that we don't monitor the os keyboard setting changes dynamically, so you need to restart Firefox after changing the setting.
|
||
Comment 9•5 years ago
|
||
(In reply to Edgar Chen [:edgar] from comment #8)
In MAC the tab-navigation behavior depends on the OS Keyboard setting.
Enabling "Full Keyboard Access" in the Keyboard preference would make link tab navigable.
Note that we don't monitor the os keyboard setting changes dynamically, so you need to restart Firefox after changing the setting.
The number of duplicates and similar bugs filed only recently suggests that something regressed here. Somebody should take a closer look.
|
|
||
Updated•5 years ago
|
|
|
||
Updated•5 years ago
|
|
|
||
Updated•5 years ago
|
|
||
Comment 12•5 years ago
|
||
I'm unclear what the bug is here. Tab navigation of links seems to work ok for me.
|
|
||
Comment 13•5 years ago
|
||
I don't know and can't check myself -- I only saw a number of bugs filed on this recently in Firefox::Keyboard Navigation (see Duplicates and See Also).
|
||
Comment 14•5 years ago
|
||
[:edg(In reply to Edgar Chen [:edgar] from comment #8)
In MAC the tab-navigation behavior depends on the OS Keyboard setting.
Enabling "Full Keyboard Access" in the Keyboard preference would make link tab navigable.
Note that we don't monitor the os keyboard setting changes dynamically, so you need to restart Firefox after changing the setting.
I'm not sure which specific control you are referring to in Keyboard Preferences. If you are talking about the "Use keyboard navigation to move focus between controls" then I can tell you that since updating to macOS Catalina, that stopped working for me and I had to set accessibility.tabfocus to 7 in about:config, to make tabbing links work. Is there another control in preferences that I should be using? There is nothing obvious there to me. I am sure you will agree that asking anyone who requires the use of a keyboard to navigate to open about:config is not an acceptable solution. That should be for developer use only, not making the web accessible to disabled people.
|
|
||
Comment 15•5 years ago
|
||
Note that we don't monitor the os keyboard setting changes dynamically, so you need to restart Firefox after changing the setting.
It shouldn't require restarting and doesn't when chrome elements are being navigated. It looks like the keyboard navigation setting state change isn't being propagated down to child processes.
That isn't really a regression though, at least not since multiple processes have been enabled, and I don't see any different behaviour in 10.15
The 'keyboard navigation' preference appears to operate the same in 10.15 although the UI for it was reworded.
|
|
||
Comment 16•5 years ago
|
||
I filed bug 1600430 on the child process issue.
|
||
Comment 18•4 years ago
|
||
Hi, I tried to reproduce this issue on MAC os 10.15.2 with our latest Nightly build as well as Beta 73.0b8 in order to find a regression range but if you set the "Use keyboard navigation to move focus between controls" options in Systems preferences everything works fine. Is this still a valid issue ? if so can someone provide some steps on how to reproduce it ? maybe a test page ?
@mfishe@gmail.com Since this stopped working for you If you're willing, we have a tool called mozregression that will automate the process of downloading various builds from our development cycles to narrow down the change that's causing problems. Information on the tool is available at http://mozilla.github.io/mozregression/. A command like |mozregression --good 2018-10-01 --bad 2020-01-21 should be enough to get started (assuming Fx64 was ok). Thanks!
|
|
||
Comment 19•4 years ago
|
||
(In reply to Rares Doghi from comment #18)
Hi, I tried to reproduce this issue on MAC os 10.15.2 with our latest Nightly build as well as Beta 73.0b8 in order to find a regression range but if you set the "Use keyboard navigation to move focus between controls" options in Systems preferences everything works fine. Is this still a valid issue ? if so can someone provide some steps on how to reproduce it ? maybe a test page ?
@mfishe@gmail.com Since this stopped working for you If you're willing, we have a tool called mozregression that will automate the process of downloading various builds from our development cycles to narrow down the change that's causing problems. Information on the tool is available at http://mozilla.github.io/mozregression/. A command like |mozregression --good 2018-10-01 --bad 2020-01-21 should be enough to get started (assuming Fx64 was ok). Thanks!
Sorry for the late reply. I see it is now working for me. I am not sure when this started working, so can't say what might have been the problem.
|
|
||
Comment 20•4 years ago
|
||
Since this issue no longer occurs I will close it as Works for Me but if it starts to reoccur please reopen it.
Also if you are able to reproduce this issue can you please perform a mozregression in order to pin point the cause of it ?
|
|
||
Comment 21•4 years ago
|
||
(In reply to Rares Doghi from comment #20)
Since this issue no longer occurs I will close it as Works for Me but if it starts to reoccur please reopen it.
Also if you are able to reproduce this issue can you please perform a mozregression in order to pin point the cause of it ?
OK cool, will do. Still working for me too though.
Description
•