Bug 137046

Summary:	Date.parse being calculated incorrectly on Safari 7
Product:	WebKit	Reporter:	Darshan <shroffdarshan>
Component:	JavaScriptCore	Assignee:	Nobody <webkit-unassigned>
Status:	NEW
Severity:	Critical	CC:	ap, ggaren, mark.lam
Priority:	P1	Keywords:	InRadar
Version:	528+ (Nightly build)
Hardware:	Mac
OS:	OS X 10.9

Darshan

Reported 2014-09-23 15:13:08 PDT

I am in Pacific Timezone. Today is 23rd Sept 2014, 3 PM on my local system DST will end on Nov 02, 2 AM On Chrome (37.0.2062.122), Safari 6 new Date(Date.parse("2014/11/02 3:00")) shows up as "Sun Nov 02 2014 03:00:00 GMT-0800 (PST)" On Safari Version 7.0.6 (9537.78.2) new Date(Date.parse("2014/11/02 3:00")) shows up as "Sun Nov 02 2014 02:00:00 GMT-0800 (PST)" It seems to be a bug on Safari 7 Also is there a bug report already present for this issue.

Attachments
Add attachment proposed patch, testcase, etc.

Alexey Proskuryakov

Comment 1 2014-09-23 19:27:07 PDT

Could you please elaborate why this is a bug, and why it is critical for you? 2am and 3am is the same time this day.

Darshan

Comment 2 2014-09-30 10:59:19 PDT

Thats not true. Here is the sequence of the times on 2nd Nov in California. 12.30 AM PDT 1.00 AM PDT 1.30 AM PDT 1.59 AM PDT 2.00 AM PDT or 1.00 AM PST 1.30 AM PST 2.00 AM PST 2.30 AM PST 3.00 AM PST 3.30 AM PST Its a critical bug, because it causes a large amount of issues with any implementation related to DST switch days's

Geoffrey Garen

Comment 3 2014-09-30 15:50:33 PDT

<rdar://problem/18507865>

Note You need to log in before you can comment on or make changes to this bug.