It may seem that the 2000 problem is most likely to bite 25-year-old legacy applications written in Cobol. But the fact is today's Inter-net technology is not immune to the malaise.
Clearly, most developers will not find this as daunting a task as bringing 100 million lines of Cobol into Year 2000 compliance, but it is an issue that needs to be addressed.
The Netscape documentation also refers to several date-related methods including getYear, which "returns the year in the specified date [object]", and toLocaleString, which "converts a date to a string, using the current locale's conventions".
According to the documentation, "the getYear method returns either a two-digit or four-digit year: for years between and including 1900 and 1999, the value returned by getYear is the year minus 1900. For years less than 1900 or greater than 1999, the value returned by getYear is the four-digit year". This seems to contradict the Date object documentation's statement.
InfoWorld testing revealed that both Navigator 3.01 and Navigator 4.01 in Netscape's Communicator will correctly store four-digit dates of years from 100 AD until 2999 AD. However, Netscape browser's version of toLocaleString will correctly display dates prior to 1900.
Also, IE 3.02 doesn't work at all with dates before 1970. Microsoft has fixed most of the inconsistencies in the beta version of IE 4.0. Dates before 1970 worked as long as four-digit years were used.