14294 2011-09-26 13:16:12 +0000 <track> Should say that the parser can return with an error state or "not processed successfully" state, so that 'error' fires instead of 'load' on <track> if the webvtt signature is wrong 2012-07-18 18:48:07 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#parsing-0 P3 blocker Unsorted 13995 14241 1 contributor ian ian mike philipj zcorpan contributor oldest_to_newest 57352 0 contributor 2011-09-26 13:16:12 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/complete/the-iframe-element.html Multipage: http://www.whatwg.org/C#parsing-0 Complete: http://www.whatwg.org/c#parsing-0 Comment: <track> Should say that the parser can return with an error state or "not processed successfully" state, so that 'error' fires instead of 'load' on <track> if the webvtt signature is wrong Posted from: 2001:4c28:a030:30:223:32ff:fec2:96fa by simonp@opera.com User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.21 Safari/535.2 58677 1 ian 2011-10-21 22:52:09 +0000 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: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: If the signature is wrong, the file won't be parsed as WebVTT, as far as I can tell. Can you elaborate? 58706 2 zcorpan 2011-10-22 12:36:37 +0000 It's just a bit confusing: [[ f the file was not successfully processed, e.g. the format in question is an XML format and the file contained a well-formedness error that the XML specification requires be detected and reported to the application, then fire a simple event named error at the track element. Note: The WebVTT format does not report errors in this fashion. ]] But if the file is not WebVTT (because the signature is wrong), we want an error event. So consider TTML, which is XML. If it contains a well-formedness error, it is by definition not XML, and therefore also not TTML. Does error fire? 58828 3 ian 2011-10-25 02:35:21 +0000 No, whether something is TTML or not is determined by the MIME type. Whether something is WebVTT or not is determined by the sniffing algorithm. At least, that's the intent. Until Adam updates his draft it's not really that way yet. Does that make sense? 58890 4 zcorpan 2011-10-25 07:22:30 +0000 I think the part I quoted above should say "if the file is of an unsupported format or cannot be successfully processed" or some such, to make sense for a UA only supporting WebVTT. Right now it reads as if a UA only supporting WebVTT would never fire 'error' since it says "The WebVTT format does not report errors in this fashion.". 58964 5 ian 2011-10-25 23:54:13 +0000 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: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Partially Accepted Change Description: see diff given below Rationale: Ok. I tweaked the text to try to avoid these problems. Let me know if it's still problematic. (Note that bug 13995 means that this isn't quite perfect yet; that's a known issue.) 58965 6 ian 2011-10-25 23:56:34 +0000 Checked in as WHATWG revision r6763. Check-in comment: Clarify that onerror fires if a WebVTT file has the wrong signature. http://html5.org/tools/web-apps-tracker?from=6762&to=6763