Opened 10 years ago
Last modified 5 years ago
#12633 assigned defect
dojox.form.MonthTextBox ignores min/max constraint
| Reported by: | bornmw | Owned by: | dylan |
|---|---|---|---|
| Priority: | high | Milestone: | 1.15 |
| Component: | DojoX Form | Version: | 1.6.0 |
| Keywords: | Cc: | Douglas Hays | |
| Blocked By: | Blocking: |
Description (last modified by )
dojox.form.MonthTextBox (as well as other dojox date pickers) ignores min/max constraint
Attachments (1)
Change History (7)
comment:1 Changed 10 years ago by
comment:2 Changed 10 years ago by
| Cc: | Douglas Hays added |
|---|---|
| Component: | General → DojoX Form |
| Owner: | set to dante |
We often see this complaint for dijit.form.DateTextBox and the answer is always to use the "constraints" variable rather than adjusting min/max directly. Not sure if that's the case here too or not.
comment:3 Changed 10 years ago by
| Description: | modified (diff) |
|---|
comment:4 Changed 9 years ago by
| Type: | enhancement → defect |
|---|
YearTextBox?'s popup widget was not populating disabled years.
Changed 9 years ago by
| Attachment: | 12633.patch added |
|---|
year constraints failing since disabled year labels were not populated, month constraints failing since this._year is not defined
comment:5 Changed 5 years ago by
| Milestone: | tbd → 1.12 |
|---|---|
| Owner: | changed from dante to dylan |
| Status: | new → assigned |
comment:6 Changed 5 years ago by
| Milestone: | 1.13 → 1.15 |
|---|
Ticket planning... move current 1.13 tickets out to 1.15 to make it easier to move tickets into the 1.13 milestone.
Note: See
TracTickets for help on using
tickets.
Sorry, just found out that YearTextBox? supports min/max But it is very buggy When I specify max value
<input id="endDateInputAnn" dojoType='dojox.form.YearTextBox' name="startDate" constraints="{datePattern:'MM/dd/yyyy', max:'2009-01'}">it displays two years (2008 and 2009) on 2008 - 2019 page, when I move to 2020 - 2031 page it still displays two years (2008 and 2009), crossed out though.