-
Notifications
You must be signed in to change notification settings - Fork 229
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
tab is always prevented #110
Comments
I'd like to see either of these suggestions implemented. |
I've got this implemented in #111 and I'm using it as of now. |
You could do something like this. It's not pretty, but it will get you moving forward in a bind.
|
Are either of the mentioned PR's going to be merged? I would like to TAB to other input fields after a selection is made also. |
@twuerker - I'd like to pick @clalimarmo's #140, which has docs but a merge conflict. Ideally there would be a short test case as well. If either of you update the PR, I'm more than happy to merge it in. |
I think that regardless of the caret navigation, the tabbing shouldn't exist as currently you can't tab through even if you've selected an item. The arrow key navigation should be purely up/down/enter and shouldn't be messing with the tabbing. It's the most logical solution and the most intuitive one. Any progress on this? |
I think the behaviour behind the TAB key is not good as it is... When I press tab the component picks the first option, which is nice, but if I press tab again I should go to the next focusable element in HTML. Moreover, I think this should happen when you hit TAB the first time.
What are your thoughts?
The text was updated successfully, but these errors were encountered: