Keyboard focus is getting lost after activating home control in left navigation pane in windows.
- Dominant language
- JavaScript
- Stars
- 31.5k
- Forks
- 5.8k
- Avg merge
- 9d 8h
- Merged PRs (30d)
- 2
Description
### Description
**User Impact:**
Keyboard dependent users will find it difficult to identify the currently focused element if keyboard focus is getting lost after activating home control in left navigation pane in windows.
**Refer Attachment:**
1. Keyboard focus get lost after activating Home tab item present in left navigation pane.mp4
https://github.com/user-attachments/assets/9c3f3f02-2faa-4307-ba14-f80c3c7c7bde
### Expected behavior
Keyboard focus shouldn't be lost home tab item after activating it, it should remain on the home control.
### Actual behavior
Keyboard focus is getting lost after activating home control in left navigation pane in windows.
On press tab key, focus is moving to 'Github' control.
### Steps to reproduce
1. Open the URL: https://docs.pwabuilder.com/#/builder/android in latest edge browser.
2. PWA Builder - packaging page will be displayed on screen.
3. Press tab key to reach 'Ham burger menu button' and activate it.
4. Now press tab key to reach to the home control and activate it.
5. Verify whether keyboard focus is getting lost after activating home control in left navigation pane in windows or not.
### Environment
OS: Windows 11 Enterprise Insider Preview Version 24H2 (OS Build 26100.3775)
Browser Microsoft Edge Version 135.0.3179.85 (Official build) (64-bit)
URL: https://docs.pwabuilder.com/#/builder/
### Additional Information
- [ ] Bug still occurs when all/other plugins are disabled?
Contributor guide
Research direction
Start by reproducing the focus behavior at https://docs.pwabuilder.com/#/builder/android in Microsoft Edge on Windows, following the listed keyboard steps. Trace the left navigation and Home control implementation; done means activating Home leaves focus on the Home control and the next Tab moves from that control rather than directly to Github.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100