fix: set the focus starting point without a fragment navigation - #16992
fix: set the focus starting point without a fragment navigation#16992Nic-Polumeyv wants to merge 3 commits into
Conversation
|
Install the latest version of pnpm add https://pkg.svelte.dev/@sveltejs/kit/c/9a1d4811c0cb2f5a69bf982740f471e95516e7b8Open in |
🦋 Changeset detectedLatest commit: 9a1d481 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
1 participant
Fixes #16982.
Firefox and WebKit drop the focus a frame after
tabindexis removed rather than synchronously, so the two starting-point tests poll for<body>instead of readingactiveElementonce. The target now receives afocus/blurpair it never got from a fragment navigation, which is the trade-off teemingc named in #10856.