#8521 closed defect (fixed)
[patch][ccla]DateTextBox: shows duplicate dates in some timezones.
| Reported by: | yoman | Owned by: | Adam Peller |
|---|---|---|---|
| Priority: | high | Milestone: | 1.3 |
| Component: | Dijit - Form | Version: | 1.2.0 |
| Keywords: | Cc: | Bryan Forbes | |
| Blocked By: | Blocking: |
Description (last modified by )
On you desktop PC go to control Panel > Date,Time,Language,and Regional Options > Change the date and time > Choose “(GMT-4:00)Santiago” On your page, if you have a datebox, open it and navigate to October 2008, oct 10 appear twice, while Oct 11 is missing:
I found out what is causing this problem: In Santiago timezone (also Manaus and Brasilia) they are changing to daylight savings time at 12 AM which causes the javascript new Date() to fail and return the previous day, as 12AM 11 Oct 2008 isn't a valid date.
Attachments (2)
Change History (8)
Changed 13 years ago by
| Attachment: | calendar.jpg added |
|---|
comment:1 Changed 13 years ago by
| Description: | modified (diff) |
|---|---|
| Owner: | set to Adam Peller |
| Summary: | DateTextBox shows duplicate dates in some tiemzones. → DateTextBox: shows duplicate dates in some timezones. |
comment:2 Changed 13 years ago by
| Cc: | Bryan Forbes added |
|---|
Changed 13 years ago by
| Attachment: | brazilcal.patch added |
|---|
Use 1AM for all Date calculations to avoid DST problems
comment:3 Changed 13 years ago by
| Milestone: | tbd → 1.3 |
|---|---|
| Summary: | DateTextBox: shows duplicate dates in some timezones. → [patch][ccla]DateTextBox: shows duplicate dates in some timezones. |
comment:4 Changed 12 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:5 Changed 12 years ago by
comment:6 Changed 10 years ago by
| Component: | Dijit → Dijit - Form |
|---|
Note: See
TracTickets for help on using
tickets.
Did you mean October 2009, as pictured? I can't seem to recreate this on a Mac. Is it dependent on the time of day you run the test? I think there was another ticket on this somewhere.
I wonder if using "12:01AM" in the Date object we use to calculate days on the calendar would solve the problem without breaking something else?