#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 )
Hi,
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 12 years ago by
Description: | modified (diff) |
---|---|
Milestone: | tbd → 1.3 |
Summary: | FilteringSelect reject empty input → FilteringSelect: rejects empty input |
comment:2 Changed 12 years ago by
Resolution: | → worksforme |
---|---|
Status: | new → closed |
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 10 years ago by
Component: | Dijit → Dijit - Form |
---|