Repository navigation
feat(services): add roving keyboard navigation to the dashboard list - #648
Open
woahwhattheheck wants to merge 7 commits into
Open
woahwhattheheck wants to merge 7 commits into
woahwhattheheck wants to merge 7 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #633
/claim #633
The services list now has one active primary-link tab stop. ArrowUp/ArrowDown move focus with wrapping, Home/End jump to the boundaries, and Enter/Space activate the focused link. Active service identity stays synchronized when sorting or replacing the list, with native list/link semantics and visible focus retained.
Unit and integration coverage was authored for the requested keyboard behaviors, including actual Tab entry. The pure navigation helper passed strict TypeScript compilation and nine runtime assertions. The existing fork CI stopped at npm ci because package.json and package-lock.json on the sponsor base request incompatible jest-dom and ESLint versions; build and Jest did not execute. No dependency or lockfile changes are included.
I am claiming this contribution under @woahwhattheheck and requesting the applicable GrantFox OSS/FWC26 bounty payment. Please confirm assignment, reward eligibility and amount, and the settlement process.