Available options do not have two-way bindings about angular-selectize HOT 5 CLOSED

If an option has been selected, Selectize's default behavior is to hide it from the option dropdown. Try adding this to your config: hideSelected:false

I could not reproduce the problem using the demo plnkr from the readme: http://plnkr.co/edit/4J6IUj?p=preview

from angular-selectize.

The selects aren't bound to the same model - they are bound to the same list of options. The options are not two-way bound. I'll play with the plnkr to reproduce.

from angular-selectize.

Oh, I understand now. Ya, send me the plnkr and I'll see what I can do

On Wed, Jul 30, 2014 at 8:56 AM, Derek Prior [email protected]
wrote:

The selects aren't bound to the same model - they are bound to the same
list of options. The options are not tw-way bound. I'll play with the plnkr
to reproduce.

—
Reply to this email directly or view it on GitHub
#7 (comment)
.

from angular-selectize.

Here it is: http://plnkr.co/edit/MdTHHn5qF4Umc2G9MYR2?p=preview

1. Add "green" to the first input.
2. Notice that myOptions is updated to include the new option.
3. Go to the second input and start typing "green".

It does not autocomplete despite being in myOptions.

from angular-selectize.

I tried using a private scope but didn't have any success after trying for
a half hour or so. If you can get this to work let me know.

On Wed, Jul 30, 2014 at 9:01 AM, Derek Prior [email protected]
wrote:

Here it is: http://plnkr.co/edit/MdTHHn5qF4Umc2G9MYR2?p=preview

1. Add "green" to the first input.
2. Notice that myOptions is updated to include the new option.
3. Go to the second input and start typing "green".

It does not autocomplete despite being in myOptions.

—
Reply to this email directly or view it on GitHub
#7 (comment)
.

from angular-selectize.