W3C home > Mailing lists > Public > public-media-fragment@w3.org > March 2011

Re: Safari 5.0.4 ISO 8601 Date Parsing

From: David Singer <singer@apple.com>
Date: Wed, 23 Mar 2011 18:14:16 +0100
Cc: eric.carlson@apple.com, Media Fragment <public-media-fragment@w3.org>
Message-Id: <5444E9ED-4A70-47C6-A918-F189A777BE1F@apple.com>
To: Thomas Steiner <tomac@google.com>
Thomas, hi

we're aware of the bug...I am following the breadcrumb trail on it.  I wonder...have you checked the webkit nightlies?  If it works there, we can hope, and I can stop following breadcrumbs!

On Mar 23, 2011, at 11:17 , Thomas Steiner wrote:

> Hi Eric and David,
> 
> RaphaŽl Troncy from the W3C Media Fragments WG (that I'm also part of)
> suggested to get in touch with you with regards to the Safari 5.0.4
> bug with the ID 9167763 opened by me
> (https://bugreport.apple.com/cgi-bin/WebObjects/RadarWeb.woa/22/wo/P1GRst1tM9Fhft9riLkA2M/12.83.28.0.9,
> not sure if the URL works for you, or only with my Apple log-in). The
> problem is mainly that Date.parse('2007-03-01T13:00:00Z') returns NaN,
> where it should return the timestamp 1172754000000. While ISO 8601
> date parsing is defined in ECMA Script 5, my understanding is that
> Safari (JavaScriptCore) currently implements ECMA Script 3 (but I
> might be wrong here), so ISO 8601 dates are not required to be
> working. However, and this is mainly why I opened this bug, WebKit
> 5.0.4 correctly parses ISO 8601 dates, plus all other browsers that I
> have tested (see the bug for concrete details). Could you maybe shine
> some light on the situation?
> 
> Thank you very much!
> 
> Best,
> Tom
> 
> -- 
> Thomas Steiner, Research Scientist, Google Inc.
> http://blog.tomayac.com, http://twitter.com/tomayac

David Singer
Multimedia and Software Standards, Apple Inc.
Received on Wednesday, 23 March 2011 17:14:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:52:46 UTC