Closed
Bug 129662
Opened 22 years ago
Closed 20 years ago
javascript Date.getYear not y2k compliant
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
People
(Reporter: markus, Assigned: rogerl)
References
()
Details
It returns 8.3.102 for me. it should be 8.3.2002, of course. Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020212
Comment 1•22 years ago
|
||
*** This bug has been marked as a duplicate of 100123 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Comment 2•22 years ago
|
||
Marking Verified. Please see the duplicate bug for more links and more details; for example, this summary: Summary: getYear is depreciated in ECMA-262 and only getFullYear is necessary for compliance. Since getYear was returning 101 for 2001 as of 4.06, they decided to keep this behavior.
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Status: VERIFIED → UNCONFIRMED
Resolution: DUPLICATE → ---
Comment 3•20 years ago
|
||
*** This bug has been marked as a duplicate of 22964 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago → 20 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•