forked from mirrors/gecko-dev
d07b087748
Give `tabindex` attributes to each focusable element and handle enter keypresses (via the `dialogaccept` event) on them. The tab index ordering is: 1. Accept button (initial focus) 2. Settings button 3. Learn more 4. Not now Also give `#infoBody` a tab index of -1 so it doesn't receive focus. It does normally for some reason. The accept button still does not have a focus ring initially. When you hit tab the first time, the focus ring appear on the settings button. IMO it's better not to show the ring initially since most people won't be interacting with the dialog with the keyboard, and even those that do don't necessarily need to see it initially. If we do want it initially, calling `focus` on the button in a load event listener works. On Windows (and maybe Linux?), the arrow keys still move around the elements until the focus gets stuck on the Not now link. After that the arrow keys don't work anymore but the tab key still does. Not sure how to fix that part. Differential Revision: https://phabricator.services.mozilla.com/D125616 |
||
|---|---|---|
| .. | ||
| firefoxSuggest.ftl | ||
| interventions.ftl | ||
| preloaded-top-urls.json | ||
| quicksuggestOnboarding.css | ||
| quicksuggestOnboarding.js | ||
| quicksuggestOnboarding.xhtml | ||
| quicksuggestOnboarding_illustration.svg | ||
