This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The string --> needs to be banned from the allowed syntax in cue data. Examples: <c.-->foo <v -->foo foo-->
(In reply to comment #0) > The string --> needs to be banned from the allowed syntax in cue data. Why? It might have some unexpected effects, but it's not invalid, IIUC. > Examples: > > <c.-->foo This parses to <span class="--">foo > <v -->foo This parses to <span title="--">foo > foo--> This parses to foo--> IIUC.
See step 43 in http://dev.w3.org/html5/webvtt/#webvtt-parser-algorithm (basically --> in cue data starts a new cue)
(In reply to comment #2) > See step 43 in http://dev.w3.org/html5/webvtt/#webvtt-parser-algorithm > (basically --> in cue data starts a new cue) Ah yeah, that's right, I remember. It also helps to "hide" comments. But that doesn't mean it needs banning from cue data, does it?
(In reply to comment #3) > Ah yeah, that's right, I remember. You sure what you remember isn't what the spec said before it was changed to make "-->" aggressively start a new cue? > It also helps to "hide" comments. No. > But that doesn't mean it needs banning from cue data, does it? It does.
Oops, yeah, not sure why I forgot to do this when I changed the parser.
Checked in as WHATWG revision r7451. Check-in comment: Make --> in cue payloads non-conforming since it won't be parsed right anyway. http://html5.org/tools/web-apps-tracker?from=7450&to=7451
Hi, I have a problem with this fix. What if I carry XML data (including XML comments) in the payload of a VTT metadata cues? The --> (end of comment) will be present and since the cue is a metadata cue, it won't be escaped.
Cyril, please file a new bug. This was just making the allowed syntax match what the parser already does.
Done: https://www.w3.org/Bugs/Public/show_bug.cgi?id=19465