CanJS can-value does not work for multi-select when options are rendered using Map #1414

Closed
neildcruz19 opened this Issue Jan 22, 2015 · 1 comment

Comments

Projects
None yet
3 participants
@neildcruz19

There seems to be an issue with Multi-selects when rendering using can-value.

Here is a link to the issue:

http://stackoverflow.com/questions/27759924/canjs-can-value-does-not-work-for-multi-select-when-options-are-rendered-using-m

@neildcruz19

This comment has been minimized.

Show comment
Hide comment
@neildcruz19

neildcruz19 Jan 22, 2015

Im seeing another issue with the can-value for select inputs in chrome maybe caused due to the element not being ready when the timeout occurs:

 // This may happen in some edgecases, esp. with selects that are not in DOM after the timeout has fired
if (!this.element) {
    return;
}

Im seeing another issue with the can-value for select inputs in chrome maybe caused due to the element not being ready when the timeout occurs:

 // This may happen in some edgecases, esp. with selects that are not in DOM after the timeout has fired
if (!this.element) {
    return;
}

asavoy added a commit to asavoy/canjs that referenced this issue Feb 6, 2015

Added failing test to prove #1414 - <select multiple can-value"..."> …
…will not apply the initial value if dynamically rendering the <option> tags.

asavoy added a commit to asavoy/canjs that referenced this issue Feb 6, 2015

Fix failing test for #1414; Multiselect.set() should not be called im…
…mediately in init() so that any dynamic <option> tags can finish rendering. This is similar to how Value.init() works for <select>.

@daffl daffl added this to the 2.2.0 milestone Feb 6, 2015

@justinbmeyer justinbmeyer added the bug label Feb 11, 2015

@daffl daffl closed this in #1427 Feb 13, 2015

@daffl daffl removed the fixed in branch label Feb 20, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment