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 11647 - Use exactly 2 digits for hours in WebVTT timestamps
Summary: Use exactly 2 digits for hours in WebVTT timestamps
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
Depends on:
Reported: 2011-01-02 21:22 UTC by contributor
Modified: 2011-08-04 05:35 UTC (History)
5 users (show)

See Also:


Description contributor 2011-01-02 21:22:39 UTC

Use exactly 2 digits for hours in WebVTT timestamps

Posted from:
Comment 1 Philip J├Ągenstedt 2011-01-02 21:23:46 UTC
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

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

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 Ian 'Hixie' Hickson 2011-02-03 21:06:57 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: Rejected
Change Description: no spec change
Rationale: Don't forget that this stuff applies to infinitely streaming videos. I think it's perfectly reasonable to expect kiosks to be streaming videos for months at a time, let alone more than 4 days, and one can totally imagine that in such a scenario a script might be adding cues onto a video that is playing at a point longer than 100 hours.
Comment 3 Michael[tm] Smith 2011-08-04 05:35:56 UTC
mass-move component to LC1