Closed
Bug 599802
Opened 14 years ago
Closed 14 years ago
Firefox 4 returns wrong time using new Date()
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 591845
Tracking | Status | |
---|---|---|
blocking2.0 | --- | betaN+ |
People
(Reporter: jarben, Unassigned)
Details
(Keywords: regression)
Attachments
(1 file)
81 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b6) Gecko/20100101 Firefox/4.0b6
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b6) Gecko/20100101 Firefox/4.0b6
if you call new Date() FF3 and FF4 have different results where FF4 is not correct
Reproducible: Always
Steps to Reproduce:
try document.write(new Date()); in FF3 and FF4
Actual Results:
FF4 - Sun Sep 26 2010 18:44:09 GMT-1100 (New Zealand Standard Time)
FF3 - Mon Sep 27 2010 18:44:46 GMT+1300 (New Zealand Daylight Time)
Expected Results:
FF4 - Mon Sep 27 2010 18:44:09 GMT+1300 (New Zealand Daylight Time)
FF3 - Mon Sep 27 2010 18:44:46 GMT+1300 (New Zealand Daylight Time)
Reporter | ||
Comment 1•14 years ago
|
||
Comment 2•14 years ago
|
||
paul loves it when the antipodes undergo a daylight-time transition.
Comment 3•14 years ago
|
||
Possibly a regression from bug 591845?
Updated•14 years ago
|
blocking2.0: --- → ?
Keywords: regression
Comment 4•14 years ago
|
||
I can reproduce this on Vista x64 using 4.0b6 but not the latest nightly. I think that the fix for bug 591845 did not get in until after 4.0b6 was released.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Comment 5•14 years ago
|
||
Ah, hmm. Does the "Target Milestone" on checked-in bugs in JS-land not correspond to the release the bug was fixed for?
Updated•14 years ago
|
blocking2.0: ? → betaN+
You need to log in
before you can comment on or make changes to this bug.
Description
•