#16828 closed defect (fixed)
CheckedMultiSelect: "TypeError: Cannot read property '0' of undefined
Reported by: | omega | Owned by: | omega |
---|---|---|---|
Priority: | undecided | Milestone: | 1.8.4 |
Component: | DojoX Form | Version: | 1.8.3 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description (last modified by )
Line 316 of CheckedMultiSelect.js in dojox seems to be experiencing an issue.
If I change it to pull item.id as opposed to item.value[0], things start working.
I guess this has to use the idProperty of the store perhaps? Just a guess, I'm not 100% sure of the lifecycle here, I just know what to poke to get things working...
Attachments (1)
Change History (6)
comment:1 Changed 8 years ago by
Description: | modified (diff) |
---|---|
Owner: | changed from dante to omega |
Status: | new → pending |
comment:2 Changed 8 years ago by
Also, do you really want the store to indicate the initially selected items, rather than using the value attribute? And if yes, were you expecting updates to the CheckedMultiSelect to be reflected back to the store? There's no code for that AFAIK.
comment:3 Changed 8 years ago by
Status: | pending → new |
---|
Here's how I'm instantiating one where the hidden select remains empty and I can't check options:
Changed 8 years ago by
Attachment: | CheckedMultiSelectTest.html added |
---|
Hopefully this works for you...
comment:4 Changed 8 years ago by
Milestone: | tbd → 1.8.4 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Reproduced the failure (where clicking the radio buttons has no effect) on 1.8.3, but it's fixed in 1.8.4, thanks to [30568]. That's a backport of a bunch of changes; I didn't trace down the real change that fixed it.
How do you reproduce the problem?