I think one should use a DateTimeFormat, and we should leave Date.parse()
as a thin wrapper around the JS equivalent.
We might have an opportunity to make things different when we'll emulate
JSR 310 (from Java 8)
On Thursday, October 17, 2013 7:34:22 PM UTC+2, Daniel Kurka wrote:
>
> Hi all,
>
> IE10 does not handle dates the same way other browser do anymore. This
> breaks a test in the EmulSuite.
>
> // IE10 (Standards mode)
> >> new Date(Date.parse("3/31/2000")).toUTCString()
> "Fri, 31 Mar 2000 07:00:00 UTC"
>
> // IE9 (Standards mode) and previous versions of IE
> >> new Date(Date.parse("3/31/2000")).toUTCString()
> "Fri, 31 Mar 2000 08:00:00 UTC"
>
> MS now uses windows time zones to calculate historic dates, see:
>
> http://blogs.msdn.com/b/ie/archive/2013/03/25/spring-forward-advancing-historical-date-and-time-calculations-on-the-web.aspx
>
>
>
> On the Java side:
>
> http://docs.oracle.com/javase/7/docs/api/java/util/Date.html#parse(java.lang.String)
>
> "Once the entire string s has been scanned, it is converted to a time
> result in one of two ways. If a time zone or time-zone offset has been
> recognized, then the year, month, day of month, hour, minute, and second
> are interpreted in UTC and then the time-zone offset is applied. Otherwise,
> the year, month, day of month, hour, minute, and second are interpreted in
> the local time zone."
>
> I appreciate input on this!
>
> -Daniel
>
>
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
