#8917 closed enhancement (fixed)
FilteringSelect: If required="false", set custom valid DefaultValue
Reported by: | thekryz | Owned by: | |
---|---|---|---|
Priority: | high | Milestone: | 1.5 |
Component: | Dijit - Form | Version: | 1.2.3 |
Keywords: | FilteringSelect displayedvalue validation | Cc: | |
Blocked By: | Blocking: |
Description
At the moment (since [13989]) with a FilteringSelect? and required="false", it is okay to leave the FilteringSelect? blank and it will be accepted when submitting a form. My suggestion is, that a user can enter a custom Default Value (other than the atm hard-coded "") for the FilteringSelect?.
My reason for this: I am using FilteringSelects? in my form, that display a default value using displayedvalue like this:
<select dojotype="dijit.form.FilteringSelect" displayedvalue="Please choose" required="false" name="myName"> <option value="#LOW">Low</option> <option value="#HIGH">High</option> </select>
Now I have some FilteringSelects? on the page that are required, but this one is not supposed to be. I'd therefor like my displayedvalue to be "valid" in the sense that the FilteringSelect? returns no value, but doesn't show me that it's invalid and can send the form.
This is also about a better handling of Default Values in FilteringSelects? - maybe the two issues can have one solution?
Change History (5)
comment:1 Changed 12 years ago by
comment:2 Changed 12 years ago by
Milestone: | 1.4 → future |
---|
comment:3 Changed 11 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
We now have the placeHolder attribute on all TextBox? widgets that does exactly this.
comment:4 Changed 11 years ago by
Milestone: | future → 1.5 |
---|
comment:5 Changed 10 years ago by
Component: | Dijit → Dijit - Form |
---|
I did my own custom widget for now like this:
There, you can enter an defaultValue instead of having to go with "" as a valid default.