Closed Bug 129662 Opened 24 years ago Closed 21 years ago

javascript Date.getYear not y2k compliant

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 22964

People

(Reporter: markus, Assigned: rogerl)

References

(
URL
)

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
*** This bug has been marked as a duplicate of 100123 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
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
Status: VERIFIED → UNCONFIRMED
Resolution: DUPLICATE → ---
*** This bug has been marked as a duplicate of 22964 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago → 21 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.