#8214 closed defect (fixed)
dijit.form.FilteringSelect does not reset properly
| Reported by: | ben hockey | Owned by: | Douglas Hays |
|---|---|---|---|
| Priority: | high | Milestone: | 1.3 |
| Component: | Dijit - Form | Version: | 1.2.0 |
| Keywords: | filteringselect | Cc: | |
| Blocked By: | Blocking: |
Description
when you call reset() on a FilteringSelect?, i would expect the filtering select to display an a blank value but it leaves the previous value displayed and shows a validation error.
Attachments (1)
Change History (5)
Changed 11 years ago by
| Attachment: | fsreset.html added |
|---|
comment:1 Changed 11 years ago by
| Owner: | set to Douglas Hays |
|---|
comment:2 Changed 11 years ago by
| Milestone: | tbd → 1.3 |
|---|---|
| Status: | new → assigned |
comment:3 Changed 11 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:4 Changed 9 years ago by
| Component: | Dijit → Dijit - Form |
|---|
Note: See
TracTickets for help on using
tickets.
value=null in markup is the same as value="null" (4 character string) and this is invalid since you don't have an option tag with value="null". Reset is trying to do a lookup for this value and cannot find it. When there is a error, the code tries to leave the input box unchanged and so you see the last error but the box turns yellow. Changing to value="" in the markup (or value=null in javascript) will cause the first option to be selected so that we're consistent with native html select (not sure we can change this for backward compatibility). If you set required="false", then the user can erase the input and no error will show. I'm going to use this ticket to blank out the textbox display on reset() before trying to reset the value in case there's an error (which shouldn't happen but does with this testcase).