forked from mirrors/gecko-dev
496eb6907f
Since the keyboar navigation is handled in a custom way on toolbars, it is automatically includes any element with `role="button"` in the custom focus order, overwriting the default behavior. But since we have a limited number of controls that function as a submit buttons for the URL and Search bars and this functionality is redundant for keyboard users (who could press `Enter` instead of navigating to this control and pressing an `Enter`), we want to reduce the strain of navigation and exclude those elements from the focus order - even from the custom focus handling. At the same time, we want to keep the interactive role to allow assistive technology to interact with these element, should their users choose to do so. In this patch, we are adding new `keyNav` attribute to a programmatic button and ensuring the `browser_toolbarKeyNav.js` handler does not include this element in the custom focus order. This would remove a keyboard trap created by the regressor bug 1871596 and would allow for better handling of these exceptions in the future. Differential Revision: https://phabricator.services.mozilla.com/D199309 |
||
|---|---|---|
| .. | ||
| content | ||
| jar.mn | ||
| moz.build | ||