Skip to content
This repository has been archived by the owner on Oct 2, 2019. It is now read-only.

No selectize theme multiple selection templates. #295

Closed
RobiFerentz opened this issue Oct 12, 2014 · 9 comments
Closed

No selectize theme multiple selection templates. #295

RobiFerentz opened this issue Oct 12, 2014 · 9 comments

Comments

@RobiFerentz
Copy link

No description provided.

@RobiFerentz RobiFerentz changed the title No selectize them multiple selection templates. No selectize theme multiple selection templates. Oct 12, 2014
@tannerlinsley
Copy link

Hey. This is critical!

@tannerlinsley
Copy link

👍

@deezaster
Copy link

selectize is the most beautiful theme!

@mickeyvip
Copy link

+1

@zgottlieb
Copy link

+1. Would prefer to use the Selectize theme for multiple select with the ui-select directive!

@mixalisAn
Copy link

+1

1 similar comment
@sbuljac
Copy link

sbuljac commented Feb 24, 2016

+1

@judeantony
Copy link

+1

@user378230
Copy link
Contributor

Please don't +1, use git hub reactions if you must. Better yet, consider submitting a PR! 😃

Thanks

user378230 pushed a commit that referenced this issue Sep 16, 2016
aaronroberson pushed a commit that referenced this issue Oct 19, 2016
* Added the select2 spinner on updating

* Added bootstrap refreshicon

* changed func. and added tests

* docs(README): fix angular-sanitize typo

"i" was missing in the name of "Angular-Sanitze"

* feat(selectize): add support for multiple selection 

Closes #295, closes #1787

* Fix: Quotation mark error

* Update CHANGELOG.md (#1816)

fix 0.17.0 version in changelog

* fix: ensure aria-activedescendant is correct

This is a fix for a severe error found using the Google Accessibility Developer Tool audit:
ARIA attributes which refer to other elements by ID should refer to elements which exist in the DOM.

* fix: only apply listbox role when open

This is a fix for a severe error found using the Google Accessibility Developer Tool audit:
Elements with ARIA roles must ensure required owned elements are present

* fix(bootstrap): add search role

This is a fix for a severe error found using the Google Accessibility Developer Tool audit:
Elements with ARIA roles must ensure required owned elements are present

* feature(touch): set clickTriggeredSelect to true for touchend events

Setting clickTriggeredSelect to true for "touchend" events fixes an issue I've encoutered when using this property in a search box (using ui-select-match and ui-select-choices), where we couldn't distinguish typing from clicking on an autocomplete result on mobile devices.

* Added the select2 spinner on updating

* Added bootstrap refreshicon

* changed func. and added tests

* Fix: Quotation mark error
kboga pushed a commit to kboga/ui-select that referenced this issue Nov 29, 2016
kboga pushed a commit to kboga/ui-select that referenced this issue Nov 29, 2016
* Added the select2 spinner on updating

* Added bootstrap refreshicon

* changed func. and added tests

* docs(README): fix angular-sanitize typo

"i" was missing in the name of "Angular-Sanitze"

* feat(selectize): add support for multiple selection 

Closes angular-ui#295, closes angular-ui#1787

* Fix: Quotation mark error

* Update CHANGELOG.md (angular-ui#1816)

fix 0.17.0 version in changelog

* fix: ensure aria-activedescendant is correct

This is a fix for a severe error found using the Google Accessibility Developer Tool audit:
ARIA attributes which refer to other elements by ID should refer to elements which exist in the DOM.

* fix: only apply listbox role when open

This is a fix for a severe error found using the Google Accessibility Developer Tool audit:
Elements with ARIA roles must ensure required owned elements are present

* fix(bootstrap): add search role

This is a fix for a severe error found using the Google Accessibility Developer Tool audit:
Elements with ARIA roles must ensure required owned elements are present

* feature(touch): set clickTriggeredSelect to true for touchend events

Setting clickTriggeredSelect to true for "touchend" events fixes an issue I've encoutered when using this property in a search box (using ui-select-match and ui-select-choices), where we couldn't distinguish typing from clicking on an autocomplete result on mobile devices.

* Added the select2 spinner on updating

* Added bootstrap refreshicon

* changed func. and added tests

* Fix: Quotation mark error
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

10 participants