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 11646 - step 13: copypasta in "the character at position is not a U+003A COLON character"
Summary: step 13: copypasta in "the character at position is not a U+003A COLON charac...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-02 21:02 UTC by contributor
Modified: 2011-08-04 05:14 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2011-01-02 21:02:24 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#parsing-0

Comment:
step 13: copypasta in "the character at position is not a U+003A COLON
character"

Posted from: 81.234.240.182
Comment 1 Philip Jägenstedt 2011-01-02 21:21:53 UTC 
From context, it seems that the "not" shouldn't be there.

It seems to me that the parsing of WebVTT timestamps is more convoluted than it needs to be, and that the reason is that hours can be any number of digits. In SRT it is exactly 2 and I think just going with that would be simpler. Allowing an arbitrary number of digits just makes parsing more complex and forces implementors to handle overflow in timestamps like 99999999999999999999999999:00:00.000 and using greater precision than really necessary.

There's also extra logic thrown in to not allow single-digit minutes in step 13.1.

I'd prefer exactly 2 digits for hours, limiting WebVTT to use with video files of duration shorter than 100 hours, which is hardly a practical problem.
Comment 2 Philip Jägenstedt 2011-01-02 21:24:25 UTC 
Opened a separate bug for the issue of 2-digit hours: http://www.w3.org/Bugs/Public/show_bug.cgi?id=11647
Comment 3 Ian 'Hixie' Hickson 2011-02-03 21:11:53 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: see diff given below
Rationale: Concurred with reporter's comments.
Comment 4 Ian 'Hixie' Hickson 2011-02-03 21:14:54 UTC 
Checked in as WHATWG revision r5825.
Check-in comment: VTT: copypasta that made the parsing of timestamps fail if
they had an hour component.
http://html5.org/tools/web-apps-tracker?from=5824&to=5825
Comment 5 Michael[tm] Smith 2011-08-04 05:14:17 UTC 
mass-move component to LC1