#8088 closed defect (fixed)
FilteringSelect - required defaults to true
Reported by: | ben hockey | Owned by: | Douglas Hays |
---|---|---|---|
Priority: | high | Milestone: | 1.3 |
Component: | Dijit - Form | Version: | 1.2.1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
The API says that required will default to false but it defaults to true
Attachments (2)
Change History (8)
Changed 12 years ago by
Changed 12 years ago by
comment:1 Changed 12 years ago by
Owner: | set to Douglas Hays |
---|
comment:2 Changed 12 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
[15785] Fixes #8088. Added a comment to FilteringSelect?.js to say that required defaults to true since the superclass ValidationTextBox? defaults to false. This widget uses true for a default for backward compatibility since FilteringSelect? did not like blank values in some of the older releases.
comment:3 Changed 12 years ago by
Milestone: | tbd → 1.3 |
---|
comment:4 Changed 10 years ago by
Component: | Dijit → Dijit - Form |
---|
comment:5 Changed 9 years ago by
I cannot find anything about this different default in current documentation of FilteringSelect?. Was it removed from it? If yes, why? Because the behaviour is still same (different from superclass).
comment:6 Changed 9 years ago by
required=true for FilteringSelect? but the API doc tool sometimes doesn't show all property values
Maybe we should just update the documentation (IE, add a comment in FilteringSelect?.js for that attribute)?
I forget why required=true for FilteringSelect. Perhaps for backwards-compatibility.