-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
iOS Safari "tabbing" doesn't work for non-searchable Selects #3291
Comments
Hi Have you manage to disabled the virtual keyboard with tab arrow when focusinf the input ? Best regards |
Hi @lauterry! Nope, we haven't been able to remove it. The whole searchable-by-default thing is great for user experience on desktop and pretty bad on mobile, which is why we've turned it off—but then it looks bad in iOS Safari… We're considering migrating our selects to an alternative (looking at Downshift) to get control over this part of the implementation. |
@theneva Thanks for your input |
Bug confirmed: When select was searchable, I was able to use the "tab" navigation arrow I suspect that this indeed is related to the issue described above. There is likely a workaround possible by rendering another focusable element within the select and adding an onFocus handler on it to focus on the input using refs. |
iOS Safari displays a nifty little toolbar whenever an input element is focused, which lets you skip directly to the next (or previous) input on the page.
This works as expected for the plain Select:
Working demo
Setting
isSearchable={false}
has the side effect of making the<input>
rendered by<DummyInput>
readonly
, which removes it from the tab order in iOS Safari:Broken demo
It's still in the tab order in desktop Safari, though, so… that's a thing that happens.
I tried working around this by avoiding the soft keyboard without the
readonly
attribute, but I couldn't do it, hence this issue.The text was updated successfully, but these errors were encountered: