fix: correctly set sequential focus navigation starting point when using the hash router #13860
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.
This PR fixes a regression caused by #10856 that didn't take hash routing into account when trying to set the sequential focus navigation starting point. It now correctly determines the hash and uses a cleaner fix than before with
element.focus()instead oflocation.replace(although used in a bit of a hacky way but not anymore hacky than the previous PR).I've tested on Chrome and Firefox on Windows but will need to test this on Safari too. Maybe CI can do that for me..focus()does not work on Safari and Firefox Ubuntu 😄Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
Tests
pnpm testand lint the project withpnpm lintandpnpm checkChangesets
pnpm changesetand following the prompts. Changesets that add features should beminorand those that fix bugs should bepatch. Please prefix changeset messages withfeat:,fix:, orchore:.Edits