This is as it should be, surprisingly enough. Quoting Phil Schwartau: "The upshot is d.getYear() was deprecated in the ECMA-262 standard in favor of d.getFullYear() Here are various bugs with further information on this: bug 22964 bug 45764 <--- particuarly see last comment in this one for the history of this bug 100123 bug 115264" *** This bug has been marked as a duplicate of 45764 ***
Verified "make sure you know what you're talking about"
Thanks for the reference to http://developer.netscape.com/viewsource/wyner_2k/wyner_2k.html which explains a lot. Returning more than 100 for years >2000 was considered a bug a few years ago, and as the article explains I remenber seeing the getYear() returning "2000". I didn't know the spec had changed back to what was considered a bug before... My conclusion is that using getDate() is inapprorpriate, getFullYear() should always be used.
I meant : My conclusion is that using getYear() is inapprorpriate, getFullYear() should always be used.
*** This bug has been marked as a duplicate of 22964 ***