Opened 13 years ago

Closed 13 years ago

Last modified 11 years ago

#7682 closed defect (worksforme)

FilteringSelect: rejects empty input

Reported by: jgnan Owned by:
Priority: high Milestone: 1.3
Component: Dijit - Form Version: 1.2beta
Keywords: Cc: [email protected]
Blocked By: Blocking:

Description (last modified by bill)


When I input empty value into the filtering select, the setValue() function do not call dued to it is not exists in the store result.

I encounter this problem in a special situation which the query criteria of the widget is changed following another field's value. This means I could not add a common empty item in the item store to solve this problem easily.

Futhermore, I think input empty in the FilteringSelect widget means to clear the input's value. This should be made sence to user enough but the current version seems not to support it.

Change History (3)

comment:1 Changed 13 years ago by bill

Description: modified (diff)
Milestone: tbd1.3
Summary: FilteringSelect reject empty inputFilteringSelect: rejects empty input

FilteringSelect with required=false will do what you want, I think. If not, can you attach a test case? I don't really understand your description.

comment:2 Changed 13 years ago by Douglas Hays

Resolution: worksforme
Status: newclosed

Starting with [15307] as a base, I added required="false" to the first box in dijit/tests/form/test_FilteringSelect.html. No error is shown either when an empty value is typed or when attr('value', null) is called programmatically.

comment:3 Changed 11 years ago by bill

Component: DijitDijit - Form
Note: See TracTickets for help on using tickets.