[Webkit-unassigned] [Bug 12975] Layout test failure: DST changes in US affect JavaScript date calculations

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sat Mar 10 12:16:06 PST 2007


------- Comment #11 from ddkilzer at webkit.org  2007-03-10 12:16 PDT -------
(In reply to comment #10)
> (In reply to comment #1)
> > Great catch, Kirby!  I think this illustrates how stupid JavaScript's (or is it
> > ECMAScript's?) date rules are.  Why shouldn't JavaScript dates reflect reality?

That was a poor choice of words--I apologize.  I'm sure it's not easy writing a
spec that everyone must agree to (and adhere to), especially with so much
historical data in place.  It's a no-win situation.

> I suspect that ECMAScript's rules for dates are simply a standards-ese way of
> saying "match the Windows OS system calls", because I believe Windows
> implementation of calls like these does not take historical DST into account.
> Supporting that theory is the fact that Firefox more or less matches the spec
> on Windows but does yield historical DST results on Macintosh.

However, it would be nice if the spec was clearer on whether the JavaScript
implementation could reflect the DST date/time behavior of the underlying
operating system which Firefox does now.  Of course, that would break down as
soon as someone writes an entire operating system in JavaScript, or implements
a JavaScript-interpreter-on-a-chip!

Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the webkit-unassigned mailing list