If you use the mouse to select another and then reselect the same one, it then updates correctly.
OTOH, it's because we aren't getting a change event.
If we are in fact getting a change event then this is weird and warrants more investigation (this issue has been reported before however, I suggest reviewing old issues to find them).
The "Add City" button adds a new city to the collection. Collection - it would be great if the select options could be repopulated when the collection changes. I only recently started using Stickit and am a big fan already.
In particular, if stickit knows a select is backed by an actual Backbone.
it seems that set State doesn't work anymore, but how do you pass back the value/option?
In v1.0.0, you can pass the value back in as a "full option." In this case, you are not simply passing in the value, but rather the value combined with the label.Chrome for example seems to consider each keypress to be committing the value (except for the inconsistency described above which is probably a bug or some weird corner-case).(UPDATE: Based on 43081j's comment, this inconsistency might be Angular's fault.) Firefox on the other hand, probably does not consider hitting the down arrow as committing the value (since theoretically, this could be the first in a series of clicks aiming to selected the nth value).From what I read and what I understand, most vendor do not follow the "fire on blur" rule, but instead fire the event when the element's value has been committed by the user.The problem is that each vendor seems to have their own interpretation about when a value has been commited.For my async select components, I use a get Value method.