- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
IE11 bugfix causes issues with tab order #877
Comments
This "bugfix" does indeed create a bug which prevent proper keyboard navigation in IE11. BUT it breaks "activate/focus" management in IE11. I noticed without this line that if you click in another textbox when selectize has focus, although the textbox seems focused the proper "activate/focus" events are not raised, which can cause problems, e.g. if your target textbox hosts a JS date picker. So I'm looking for something that would fix both issues! |
#406 seems to be the reason why this line of code is here. |
OK I fixed it by changing this line:
to:
i.e. I'm only focusing the next control if I know one (which fixes the "no activate/focus on click" issue and let it go otherwise (which fixes tab navigation). As far as I can tell it works nicely. Because I don't fully grasp what was creating the original problem (broken keyboard navigation), I can't say I'm 100% confident this change doesn't have adverse side-effects. |
Thanks for your efforts. I will try this modified solution in our current usage scenario. |
I've also tried this proposed fix and it has solved our IE bug as well, FWIW. I haven't done thorough testing though. |
Perfect resolution - current project I am working on requires numerous instances of the selectize menu. This proposed fix works very well. 👍 |
Original reference - selectize#877
Just realized that I had patched it that way back in August. From my point of view it is working fine too. |
Closed by #997, thanks all |
In IE 11.0 tabbing through Selectize fields is broken, try this example, focus the first field and then press tab. It should now focus the second selectize (note that there are even added tabindex properties).
The reason seems to be the bugfix for "IE11 bug: element still marked as active" in onBlur:
This causes the document's body to be focused. Removing this line resolves the issue (see this fiddle), but I am not aware about the reason why this line has been added (and what issue it is trying to fix).
The text was updated successfully, but these errors were encountered: