Repository navigation
[6.x] Use keyboard to reorder replicator sets - #15592
Merged
Merged
Conversation
… viewport so it doesn’t disappear off-screen.
…ould not fall back on the 3 dots
…d a blue left border
Stop nested Grid/Replicator sessions fighting for keys, restore focus to the moved row instead of a nested control, and only offer Move when reorder is actually possible. Also keep consumer aria-labels on DragHandle.
…p handle and the ... menu Keep move mode alive through dropdown focus teardown. After Escape, starting Move from the ⋯ menu could die immediately when focus bounced through the document. Ignore outside focus/pointer briefly after activating.
Contributor
Author
|
(Once this branch is merged I'll take a look at applying the same pattern to other areas like nav tree, Bard sets – don't want to double up prematurely!) |
…r-replicator-sets
Member
|
Jay, this is absolutely delightful to use. Thank you! I would definitely move forward on rolling this out elsewhere, starting with replacing the derpy Tree view interaction. It's kind of embarrassing how bad it was before. Sheesh. 😬 |
This was referenced Oct 23, 2026
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
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.
Description of the Problem
2026-10-06.at.16.19.06.2.mp4
For power users/keyboard users and for accessibility:
Grid and Replicator items can be reordered by dragging, but there is no reliable keyboard path to do the same. That fails WCAG reorder expectations for keyboard and screen reader users (#15390).
What this PR Does
Adds keyboard reordering for Grid (table + stacked) and Replicator sets:
⋯Move menu item↑ / ↓to reorder;EnterorEscapeto finish↑↓keycap hint shows while movingkeyboard-reorderon the publicDragHandle(existing consumers unchanged)Not in scope: Bard sets, navigation trees (those already use Alt+arrows via he-tree).
How to Reproduce