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 14954 - <track> Step 1 should be "A WebVTT cue span start tag "ruby". to coincide with Step 5.
Summary: <track> Step 1 should be "A WebVTT cue span start tag "ruby". to coincide wit...
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 blocker
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
Depends on:
Reported: 2011-11-28 20:59 UTC by contributor
Modified: 2012-07-18 18:48 UTC (History)
3 users (show)

See Also:


Description contributor 2011-11-28 20:59:53 UTC

Step 1 should be "A WebVTT cue span start tag "ruby". to coincide with Step 5.

Posted from:
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.8 (KHTML, like Gecko) Chrome/17.0.942.0 Safari/535.8
Comment 2 Michael[tm] Smith 2011-11-29 15:34:17 UTC
(In reply to comment #1)
> While the problem exists at
> it appears to have been fixed at

hmm, yeah. The multipage version is generated using a python script, and as a result of recent updates to that script, the filename for the video content became "the-video-element.html". The "video.html" filename was the one in generated previously but will not be  generating any longer. So the "video.html" file is a dead letter and should be removed.
Comment 3 Ian 'Hixie' Hickson 2011-12-07 23:56:36 UTC
Anne knows about the publishing problem and that'll be fixed.

Is the problem not present on the single-page copy?
Comment 4 Ian 'Hixie' Hickson 2011-12-09 00:27:29 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: Accepted
Change Description: no spec change
Rationale: marking fixed per comment 1; please feel free to reopen if it's not