This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html Multipage: http://www.whatwg.org/C#webvtt-cue-text-parsing-rules Complete: http://www.whatwg.org/c#webvtt-cue-text-parsing-rules Comment: WebVTT tokenizer does not consume U+003C LESS-THAN SIGN (<) Posted from: 83.218.67.122 by philipj@opera.com User agent: Opera/9.80 (X11; Linux x86_64; U; Edition Next; en) Presto/2.9.186 Version/12.00
The steps for U+003E GREATER-THAN SIGN character (>) say "abort these steps", skipping over step 8 to advance the position in input. As a result, the > will become part of the text that follow, e.g. <i>Hello would cause getCueAsHTML() to return a DOM looking like <i>>Hello.
Sounds like a mere oversight. If so, it should be a trivial fix.
> WebVTT tokenizer does not consume U+003C LESS-THAN SIGN (<) I don't follow. > The steps for U+003E GREATER-THAN SIGN character (>) say "abort these steps", > skipping over step 8 to advance the position in input. As a result, the > will > become part of the text that follow, e.g. <i>Hello would cause getCueAsHTML() > to return a DOM looking like <i>>Hello. This is now fixed.
Checked in as WHATWG revision r6553. Check-in comment: Fix the WebVTT parser to not litter the output with > characters http://html5.org/tools/web-apps-tracker?from=6552&to=6553
(In reply to comment #3) > > WebVTT tokenizer does not consume U+003C LESS-THAN SIGN (<) > > I don't follow. That was copypasta.