W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2011

[Bug 12283] <video> No indication of parsing error

From: <bugzilla@jessica.w3.org>
Date: Tue, 16 Aug 2011 04:19:31 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QtB7j-0004nM-B8@jessica.w3.org>

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #5 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-16 04:19:30 UTC ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:

Status: Partially Accepted
Change Description: see diff given below

If there was a network error and the data is incomplete, then an 'error' event
gets fired. That's already specified.

Since some formats (e.g. XML formats) report errors for syntax errors I've
added support for firing 'error' in such cases. Note that WebVTT is more like
HTML or CSS in this regard and does not distinguish syntax errors from
forward-compatible parsing rules, so WebVTT files will never fire 'error'
events in this way.

A script that wants to test for completeness in metadata tracks can always just
put a sentinel cue at the end of the file and check for it.

User agents are, of course, always allowed to report this kind of thing to the
user. Given how unlikely it is for authors to actually check for this kind of
thing, if you think it is a concern for your users, I strongly recommend that
you handle this at the UA level rather than relying on scripts.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 16 August 2011 04:19:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:01 UTC