On Mon, May 28, 2012 at 12:33 PM, David Rosen <
dro...@gmail.com> wrote:
>
> Actually the "update" part of the binding handler is sort of a hack, and I
> believe select2 could be patched to make this more elegant. What the
> "update" part does is updates the value of the "select2" if the value of the
> underlying "select" or "input" control is changed outside of the "select2".
> The problem is that it also unnecessarily does this update if the "select2"
> is changed through normal interaction, which causes the tags in the multiple
> selection example to get sorted alphabetically, and there might be other
> side effects I'm not aware of.
>
> I see two possible ways to fix this:
>
> One way is to have select2 to listen for a change on the underlying
> control's value and update itself. This would eliminate the need for the
> "update" part of the binding handler, and is probably the most compatible
> with other frameworks.