- From: <bugzilla@jessica.w3.org>
- Date: Sun, 09 Jun 2013 16:09:39 +0000
- To: public-texttracks@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22315 Bug ID: 22315 Summary: [WebVTT] Should probably allow any HTML5 space character after signature, for consistency Classification: Unclassified Product: TextTracks CG Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P2 Component: WebVTT Assignee: silviapfeiffer1@gmail.com Reporter: caitlin.potter@senecacollege.ca QA Contact: dave.null@w3.org CC: mike@w3.org, public-texttracks@w3.org "If line is more than six characters long but the first six characters do not exactly equal "WEBVTT", or the seventh character is neither a U+0020 SPACE character nor a U+0009 CHARACTER TABULATION (tab) character, then abort these steps. The file does not start with the correct WebVTT file signature and was therefore not successfully processed." In other areas of the spec (anywhere where the "skip whitespace" step is mentioned), the FORM FEED character is one of the acceptable characters. For consistency with the rest of the document, it might be a good idea to say "if the seventh character is not a space character (http://www.w3.org/html/wg/drafts/html/master/single-page.html#space-character), then abort these steps." Further, but sort of unrelated, it may be unwise to ask the parser to collect an entire line for this first step -- as if the document is not in fact a valid WEBVTT document, it could potentially be gigabytes collected before a byte 0x0A or 0x0D is encountered -- which means that for safety clients impose a maximum line length which is not defined in the standard, just to avoid going crazy trying to read a garbage document. Basically, sniffing the document could be done somewhat more cleverly. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Sunday, 9 June 2013 16:09:42 UTC