[css-nav-1] Consider candidates revealed after one scroll step?
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
Migrated from https://github.com/WICG/spatial-navigation/issues/56
Originally created by @hugoholgersson on Fri, 27 Apr 2018 14:26:33 GMT
When finding the candidate set, Chrome's spatnav includes focusables that would become visible after one (document*) scroll step in the navigated direction.
* We don't do this for scrollable divs but I consider that a bug. I believe spatnav should treat both document scrolling and element scrolling in the same way.
This behavior is not spec'ed. Should we?
Downsides:
- Trickier implementation.
Upsides:
- Better UX.
- One keystroke instead of two: [scroll + focus] instead of [scroll] + [focus].
- Focused element (and its "focus ring", if enabled) is always visible (it cannot be scrolled out).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the migrated spatial-navigation discussion and the documented behavior for candidate discovery after one document scroll step. Compare the stated upsides and downsides for document scrolling and scrollable elements, then determine whether the specification should define this behavior. Done means reaching and recording a clear resolution, since no implementation location or test is named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100