-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Cannot create property '_uiSelectChoiceDisabled' on ... #1661
Comments
I have a similar issue: Update the tagging example version to 0.18.0 and click inside the first ui-select.
plunkr: http://plnkr.co/edit/SsCE6gnNQeSOtBx0lNld?p=preview Versions: |
Reporting the same issue: |
Connected problem: ui-select modifies the data structure of the item, and it can travels back to the server. We have very strict server side validation and unknown properties are not allowed, so upgrading to version v0.18.0 broke several functions of our application. |
also encountered the issue with:
downgrading to 0.17.1 fixed the issue. |
Same problem here. Thanks mcantrell for the tip. |
0.17.1 - haven't this problem, but please fix 0.18+ |
This issue still reproduces with 0.17.1 for me. See plunker here: |
Ui-select loop over object in 0.18.0.
Then to have a nice display don't forget to print only the value :
Tips to send only the selected value and not the whole JS object you can do something like this :
|
Reporting same issue with: Console error occurs when selecting an element from the tag dropdown |
I've finally downgraded to |
+1 Angular 1.5.7 & ui-select 0.18.0
Probably caused by change on |
…selects Implement remove-selected="false" for multiple selects. This will disable a choice in the dropdown of a multiple-select element instead of removing it.
+1 |
Previously the item from the list was modified with the _uiSelectChoiceDisabled property. This allowed a leakage of information from ui-select to outside the directive. It also caused issues when the was used outside of the directive. This commit adds a reference array to store disabled items and so prevents the need to modify the item in place. Closes angular-ui#1200 and angular-ui#1661 Partially supersedes angular-ui#1641
+1 |
Previously the item from the list was modified with the _uiSelectChoiceDisabled property. This allowed a leakage of information from ui-select to outside the directive. It also caused issues when the was used outside of the directive. This commit adds a reference array to store disabled items and so prevents the need to modify the item in place. Closes angular-ui#1200 and angular-ui#1661 Partially supersedes angular-ui#1641
Fixed by #1712 |
@user378230 bug still exists in
Still triggers |
Impossible, the word Please test more thoroughly before posting in issues. Thanks! 👍 |
Indeed, my bower update went wrong and I was still using a previous version. My bad, sorry. Everything works fine now. Thanks! |
Bug description:
Directly copied from the plunker example triggers "Cannot create property '_uiSelectChoiceDisabled' on string 'blue'" (respectively for all other colors in my array).
Additionally: the demo (http://angular-ui.github.io/ui-select/demo-tagging.html) triggers "Cannot read property 'length' of undefined" if you remove the existent tags.
Link to minimally-working plunker that reproduces the issue:
Works fine in Plunker. I have no idea why.
Version of Angular, UI-Select, and Bootstrap/Select2/Selectize CSS
Angular: 1.4.10
UI-Select: 0.18.0
Bootstrap/Select2/Selectize CSS (if applicable): ~3.3.6
The text was updated successfully, but these errors were encountered: