Comments on: Javascript’s getYear() function, and other IE headaches https://lobsterpot.com.au/blog/2006/10/26/javascripts-getyear-function-and-other-ie-headaches/ Thu, 26 Oct 2006 19:05:29 +0000 hourly 1 https://wordpress.org/?v=7.0.4 By: robfarley https://lobsterpot.com.au/blog/2006/10/26/javascripts-getyear-function-and-other-ie-headaches/#comment-73 Thu, 26 Oct 2006 19:05:29 +0000 /blogs/robfarley/archive/2006/10/26/Javascript_2700_s-getYear_28002900_-function_2C00_-and-other-IE-headaches.aspx#comment-73 Woah! I had looked at that page in Firefox, where it gives an answer of 106. I guess the source of the code prints it.

Now that I look at that page in IE, it says 2006. I will correct my post. 😐

Thanks Alun.

]]> By: alunj https://lobsterpot.com.au/blog/2006/10/26/javascripts-getyear-function-and-other-ie-headaches/#comment-72 Thu, 26 Oct 2006 12:32:35 +0000 /blogs/robfarley/archive/2006/10/26/Javascript_2700_s-getYear_28002900_-function_2C00_-and-other-IE-headaches.aspx#comment-72 The link you quote demonstrates 2006 as being the correct response, and describes that dates before 1900 or after 1999 should produce a four-digit year.
As you say, though getFullYear is the correct function.
This arose because the designers of Javascript did not exactly specify the results that getYear should provide past 1999, leading to some browsers returning “06”, others returning “2006”, and some returning “106” – you can see occasional web sites even now telling you that the year is “19106” as a result.

]]>