-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
restore tabindex
after navigation
#4140
Conversation
🦋 Changeset detectedLatest commit: cf4a145 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 |
I think this is a good change - I can do some testing on an iPhone to make sure things are working as expected there. Is there a reason you chose to start focusing We'll also need to update this line in kit.svelte.dev, which assumed kit/sites/kit.svelte.dev/src/lib/search/SearchBox.svelte Lines 54 to 63 in 09bf92f
|
No technical reason—I just suspect very few users handle |
You were absolutely right about kit.svelte.dev, too. I had looked for I pushed a fix. |
Co-authored-by: Ben McCann <322311+benmccann@users.noreply.github.com>
Fixes #3501.
As noted in the issue, adding
tabindex="-1"
to<body>
causes a few focus management problems with body "stealing" input from other elements (eg. scrolling overflown children).Since it's only needed to reset the page's focus during navigation, we can safely [?] remove it afterwards.
[?]: I'm not able to test this on Apple devices.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
Tests
pnpm test
and lint the project withpnpm lint
andpnpm check
Changesets
pnpx changeset
and following the prompts. All changesets should bepatch
until SvelteKit 1.0