You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 18, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 18, 2026. It is now read-only.
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:
(dest || document.body).focus();
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).
This "bugfix" does indeed create a bug which prevent proper keyboard navigation in IE11.
Removing the lines makes tab navigation work.
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!
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.
Activity
jods4 commentedon Nov 3, 2015
This "bugfix" does indeed create a bug which prevent proper keyboard navigation in IE11.
Removing the lines makes tab navigation work.
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!
jods4 commentedon Nov 3, 2015
#406 seems to be the reason why this line of code is here.
jods4 commentedon Nov 3, 2015
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.
sb-relaxt-at commentedon Nov 3, 2015
Thanks for your efforts. I will try this modified solution in our current usage scenario.
brownbl1 commentedon Dec 16, 2015
I've also tried this proposed fix and it has solved our IE bug as well, FWIW. I haven't done thorough testing though.
bwilson-ux commentedon Feb 2, 2016
Perfect resolution - current project I am working on requires numerous instances of the selectize menu. This proposed fix works very well. 👍
Updating to remedy IE11 Tabbing issue
sb-relaxt-at commentedon Mar 3, 2016
Just realized that I had patched it that way back in August. From my point of view it is working fine too.
joallard commentedon May 28, 2016
Closed by #997, thanks all
Updating to remedy IE11 Tabbing issue