Closed
Bug 188211
Opened 22 years ago
Closed 19 years ago
(Mac-only): Date.prototype.toLocale___String() error on future dates
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: pschwartau, Unassigned)
Details
Reported by admin@dhtmlkitchen.com:
On Mac OSX and Mac9, the Date.prototype.toLocale__String() functions
error on certain dates in the future.
This problem only occurs on Mac, and not on WinNT or Linux. It occurs
somewhere between 208e10 and 209e10 milliseconds after the Unix epoch:
var dt = new Date(208e10); alert(dt.toString() + '\n' + dt.toLocaleString());
Thu Nov 29 2035 17:46:40 GMT-0800
Thursday November 29 17:46:40 2035
var dt = new Date(209e10); alert(dt.toString() + '\n' + dt.toLocaleString());
Mon Mar 24 2036 11:33:20 GMT-0800
Monday January 01 00:00:00 1900 <<<--------------- ??????????
Note the existing Mac-only bug 61184 on the toLocaleString functions:
"Date.prototype.toLocale___String() functions : GMT error"
However, this seems to be a different issue -
Comment 1•20 years ago
|
||
This date sounds quite near the one affected by the year 2038 bug, could there
be a relation ?
Some calculations can result in a year 2038 effect before year 2038, for example
time averages using (t1 + t2)/2.
Updated•19 years ago
|
Assignee: khanson → general
Flags: testcase?
QA Contact: pschwartau → general
Comment 2•19 years ago
|
||
/cvsroot/mozilla/js/tests/js1_5/Date/regress-188211.js,v <-- regress-188211.js
initial revision: 1.1
Flags: testcase? → testcase+
Comment 3•19 years ago
|
||
js1_5/Date/regress-188211.js now passes win/linux/mac 1.8.0.2, 1.8, 1.9 20060307 builds. wfm.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•