microsoft / microsoft/react-native-windows
In react-navigation on RNW: Keyboard tab is moving to previously opened screen while the current screen is being opened
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
When navigating to a new page using react-navigation, the components of a previously opened page remain in the tabindex. I think this is also related to some tabbing issues we're seeing in gallery, since we use react-navigation there (#231, #222). There's also an internal partner asking for a fix.
From react-navigation https://github.com/react-navigation/react-navigation/issues/9109:
Repro steps:
Create stack navigator with two screen (Ex: Home screen & details screen)
Go to Home screen(this screen contains few TextInputs), click a button to go to details screen
Keep hitting the TAB key. When the cursor is invisible, type few random characters. These characters are actually being typed in the Home screen's text input boxes.
Expected Behavior:
Cursor should not leave the current screen.
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 with the react-navigation issue 9109 and reproduce the stack-navigation flow described here on React Native Windows. Trace how keyboard focus and tabindex are handled when moving from Home to details. Done means TAB cannot return to the previous screen's inputs and typing affects only the current screen.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native
- Domain
- accessibility
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100