Issue metadata
Sign in to add a comment
|
Tabbing after jump to an invisible heading broken |
||||||||||||||||||||||
Issue descriptionChrome Version : 59.0.3071.115 (Official Build) (64-bit) URLs (if applicable) : What steps will reproduce the problem? (1) Jump to a heading that is visually hidden (Search + H) (2) Press tab (or Shift+Tab) What is the expected result? Tabbing should put the focus on the next interactable element in the tab order immediately following the heading. What happens instead? Tabbing puts the focus to the next element after the element that previously had focus. For example: If the keyboard focus is on a search bar at the top of the page, and the user jumps to a visually hidden h4 at the bottom of the page, then presses tab, the focus moves to the next element in the tab order immediately following the search bar (not the next element in the tab order immediately following the h4). Link to codepen: https://codepen.io/katiehockman/pen/LjPxxo - Tab to Button 1, then Jump to the visually hidden h2, then press tab (notice focus moves to button 2 instead of button 4)
,
Jul 24 2017
,
Jul 24 2017
Note that the heading is not actually "hidden" but rather offscreen, there's a big difference. To debug this I'd start with WebAXObject::SetSequentialFocusNavigationStartingPoint() and see if that's failing for some reason.
,
Oct 9 2017
Hi Katie, I noticed that this bug hasn't been updated in a while and that Dominic provided a comment. We've updated Chrome since then. I'm going to resolve this issue as archived. I encourage you to try again and reopen this issue if your problem still persists. Thanks for the through bug report and examples, they are always appreciated. Please let me know if you have any further questions. Thanks, Laura |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nyerramilli@chromium.org
, Jul 24 2017