14954 2011-11-28 20:59:53 +0000 <track> Step 1 should be "A WebVTT cue span start tag "ruby". to coincide with Step 5. 2012-07-18 18:48:53 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED WORKSFORME http://www.whatwg.org/specs/web-apps/current-work/#webvtt-cue-ruby-span P3 blocker Unsorted 1 contributor ian ian joshua.harley mike contributor oldest_to_newest 60549 0 contributor 2011-11-28 20:59:53 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html Multipage: http://www.whatwg.org/C#webvtt-cue-ruby-span Complete: http://www.whatwg.org/c#webvtt-cue-ruby-span Comment: Step 1 should be "A WebVTT cue span start tag "ruby". to coincide with Step 5. Posted from: 138.86.100.164 User agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.8 (KHTML, like Gecko) Chrome/17.0.942.0 Safari/535.8 60618 1 joshua.harley 2011-11-29 14:48:00 +0000 While the problem exists at http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#webvtt-cue-ruby-span it appears to have been fixed at http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html#webvtt-cue-ruby-span. 60623 2 mike 2011-11-29 15:34:17 +0000 (In reply to comment #1) > While the problem exists at > http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#webvtt-cue-ruby-span > it appears to have been fixed at > http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html#webvtt-cue-ruby-span. 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. 61193 3 ian 2011-12-07 23:56:36 +0000 Anne knows about the publishing problem and that'll be fixed. Is the problem not present on the single-page copy? 61274 4 ian 2011-12-09 00:27:29 +0000 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: marking fixed per comment 1; please feel free to reopen if it's not