This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 14547 - <track> In the step just before timings should there not be an end-of-file check as well? This WebVTT parser would be easier to read by the way if you did the CRLF normalization as a pre-processing step.
Summary: <track> In the step just before timings should there not be an end-of-file ch...
Status: RESOLVED WORKSFORME
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-23 01:48 UTC by contributor
Modified: 2012-07-18 18:39 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2011-10-23 01:48:55 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html
Multipage: http://www.whatwg.org/C#parsing-0
Complete: http://www.whatwg.org/c#parsing-0

Comment:
In the step just before timings should there not be an end-of-file check as
well? This WebVTT parser would be easier to read by the way if you did the
CRLF normalization as a pre-processing step.

Posted from: 1.113.239.210 by annevk@opera.com
User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.7.1; U; en) Presto/2.9.168 Version/11.51
Comment 1 Anne 2011-10-24 14:31:01 UTC 
That is, the step before the step that starts with "Timings:".
Comment 2 Ian 'Hixie' Hickson 2011-10-25 23:42:04 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:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: no spec change
Rationale: This seems to have been fixed already. This area changed quite a bit though, so let me know if it's still buggy.