(In reply to Marco Bonardo [:mak] from comment #2) > As you know, the problem with removing results navigation through TAB is that it's supported by other browsers (Chrome and now Edge Beta), it may not be trivial to change it, because even if Firefox usage of that feature is really low according to telemetry, we may not want to break incoming users expectations. I'm not fond of this argument, especially since we've got a plethora of alternative keyboard navigation methods available. If we have a genuine case for removing tab-navigation for the Awesomebar results list, than we should consider it. (Disclaimer: I haven't read through all the comments in bug 1437524 yet.)
Bug 1608766 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Marco Bonardo [:mak] from comment #2) > As you know, the problem with removing results navigation through TAB is that it's supported by other browsers (Chrome and now Edge Beta), it may not be trivial to change it, because even if Firefox usage of that feature is really low according to telemetry, we may not want to break incoming users expectations. I'm not fond of this argument, especially since we've got a plethora of alternative keyboard navigation methods available. If we have a genuine case for removing tab-navigation for the Awesomebar results list, then we should consider it. (Disclaimer: I haven't read through all the comments in bug 1437524 yet.)