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

Re: Build a Media Fragment URI Parser In JavaScript (ACTION-203)

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Fri, 6 May 2011 15:00:35 +1000
Message-ID: <BANLkTikEKO17CGmf33wGaMYoLdu2zY25uQ@mail.gmail.com>
To: RaphaŽl Troncy <raphael.troncy@eurecom.fr>
Cc: Thomas Steiner <tomac@google.com>, Media Fragment <public-media-fragment@w3.org>, Malte Ubl <malteubl@google.com>
2011/3/22 RaphaŽl Troncy <raphael.troncy@eurecom.fr>:
> Hi Thomas,
>> OK, found the issues:
>> - Strict mode (https://developer.mozilla.org/en/JavaScript/Strict_mode)
>> caused more issues than it solved. Removed for now.
> I have tried http://tomayac.com/mediafragments/mediafragments.html this
> morning. It still works on Chrome, *not* on Firefox 3.6+, Opera 11+, IE8+.
>> - Safari (not even 5.0.4) does not support ISO 8601 dates (shame).
>> Handling this correctly in the library now.
> I have seen your tweet about this. Did you file somewhere a bug report? Did
> you get an answer from Apple? We have Dave and Eric in the group who might
> help to follow up this bug.
> The home page of the media fragment includes now the announcement of this
> implementation.

Is this eventually going to be turned into a validator for media fragment URIs?

It would be nice to capture all our recent discussions about error
handling in such an application...

Received on Friday, 6 May 2011 05:01:23 UTC

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