#7838 closed defect (invalid)
Commas in dijit.form.FilteringSelect value clause cause unexpected results
Reported by: | arussell | Owned by: | |
---|---|---|---|
Priority: | high | Milestone: | 1.3 |
Component: | Dijit - Form | Version: | 1.2.0 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
If a FilteringSelect? dijit contains a comma in the value clause, things don't work as expected. Consider the following code:
<select value="comma, test" dojoType="dijit.form.FilteringSelect"> <option value="value one">one</option> <option value="comma, test">two</option> <option value="value three">three</option> </select>
You'd expect that the option with the label "two" would be selected. In Firefox 3, nothing gets selected, but Firebug reports no errors. In IE 6, an error is thrown: '0.oper' is null or not an object.
Change History (2)
comment:1 Changed 12 years ago by
Milestone: | tbd → 1.3 |
---|---|
Resolution: | → invalid |
Status: | new → closed |
comment:2 Changed 10 years ago by
Component: | Dijit → Dijit - Form |
---|
Note: See
TracTickets for help on using
tickets.
FilteringSelect? does not support specifying the widget's value attribute when option tags are used. You must use the "selected" attribute on 1 of the option tags or specify the value programmatically after the widget is created. The value attribute with a comma works OK when using a datastore. There is no value attribute on native selects either.