#3953 closed defect (wontfix)
DropdownDatePicker: Error in clearing input field when value is out of range
Reported by: | guest | Owned by: | Douglas Hays |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | Dijit | Version: | 0.4.2 |
Keywords: | Cc: | [email protected]… | |
Blocked By: | Blocking: |
Description
In version 0.4.3, DropdownDatePicker?.js contains an error at updating the generated input field with the selected date (function _updateText())
- Include the datepicker:
var element = document.getElementById("datePicker"); var startTime = new Date(); var properties = { startDate: new Date(startTime), name: "selectedDate" }; var calendarWidget = dojo.widget.createWidget("DropdownDatePicker", properties, element);
<span id="datePicker"/>
- Open the DatePicker?.
- Select a Date.
Result: The DatePicker? closes, but the generated input-field won't be updated.
Solution: Patch srcwidgetDropdownDatePicker.js, line 163 (_updateText()) from
if(this.inputNode.value < this.datePicker.startDate||this.value>this.datePicker.endDate){ this.value = ""; }
to
if(this.inputNode.value < this.datePicker.startDate||this.value>this.datePicker.endDate){ this.inputNode.value = ""; }
TIA, Michael.
P.S.: The version-dropdown below does not contains release 0.4.3, I'm leaving it empty.
Change History (4)
comment:1 Changed 14 years ago by
Milestone: | 0.4.4 → 0.9 |
---|---|
Owner: | changed from Adam Peller to Douglas Hays |
Summary: | DropdownDatePicker: Error in updating input field → DropdownDatePicker: Error in clearing input field when value is out of range |
comment:2 Changed 14 years ago by
Component: | Date → Dijit |
---|---|
Version: | → 0.4.2 |
The 0.9 DatePicker? replacement (dijit._Calendar) was completely rewritten due to these sorts of problems. Please re-open if the problem still exists in 0.9.
comment:3 Changed 14 years ago by
Milestone: | 0.9 → 0.4.4 |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
In 0.9, you can still enter a date out of range by typing in the box, but the error condition is handled properly and the node isn't cleared anymore.
Is this a problem in 0.9? I thought we disabled selection of dates that were out of range.