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 Oct 2, 2019. It is now read-only.
Previously, even when search-enabled was set to false, users could
still type in text and filter the list. This made disabling the search
feature pointless.
This fix prevents text entry to the search input and thus disables
filtering.
Fixesangular-ui#1658
* fix(searchEnabled): maintain keyboard nagivation
Fix issue where keyboard navigation was disabled when searchEnabled
was set to false.
Caused by hiding the input box which prevent key events from
propagating to the directive.
Resolved hiding the input offscreen when searchEnabled is false.
Fixesangular-ui#1059, fixesangular-ui#917, fixesangular-ui#589, fixesangular-ui#375Closesangular-ui#1543, closesangular-ui#1114, closesangular-ui#1109 (supersedes all)
* fix(selectize): show placeholder when search disabled
Previously when searchEnabled was set to false, the placeholder would
also be hidden on the selectize theme.
This fix sets the search input to disabled rather then hidden when the
searchEnabled attribute is set to false.
Fixesangular-ui#1145, fixesangular-ui#949, fixesangular-ui#691
* fix(searchEnabled): Prevent searching when disabled
Previously, even when search-enabled was set to false, users could
still type in text and filter the list. This made disabling the search
feature pointless.
This fix prevents text entry to the search input and thus disables
filtering.
Fixesangular-ui#1658
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug description:
Clicking the Disable Search button in the demo does change the label to false, but in all 3 examples the search is still active.
Link to demo:
http://angular-ui.github.io/ui-select/demo-disable-search.html
The text was updated successfully, but these errors were encountered: