Pressing Tab key on keyboard should jump to next text box in right-side panel
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- accessibility, frontend
Research direction
Reproduce the issue in the right-side Arrange panel by focusing Width and pressing Tab, then inspect the panel's focus handling and field order. Done means Tab moves through Width, Height, Left, Top, and the other fields without losing focus, with the behavior verified across the reported inputs.
Written by the indexing model from the issue text.
Description
Preflight Checklist
- I agree to follow the Code of Conduct that this project adheres to.
- I have searched the issue tracker for a feature request that matches the one I want to file, without success.
Describe the bug
Standard UI behavior is that pressing the Tab key on the keyboard jumps the focus to the next UI element, but in the right-side panels here, pressing the Tab key removes the focus from the panel entirely.
To Reproduce
- Click on an element in the canvas.
- Click on the Width input box in the right-side Arrange panel.
- Hit the Tab key on the keyboard.
- Focus disappears from the right-side Arrange panel.
Expected behavior
The focus should now be in the next field, i.e., Height, so that the user can now type in a new value in that box. Same with Left to Top boxes, and all the others.
Screenshots
draw.io version
v28.0.7
- Dominant language
- JavaScript
- Stars
- 8.2k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from jgraph/drawio
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
enhancement possible-duplicate
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug needs-info
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
bug needs-info
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
enhancement possible-duplicate
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100