19465 2012-10-11 11:11:37 +0000 Parsing issue with --> in cue 2012-10-13 05:15:10 +0000 1 1 1 Unclassified TextTracks CG WebVTT unspecified PC Windows NT RESOLVED WONTFIX P2 normal --- 1 cyril.concolato ian ian mike philipj public-texttracks silviapfeiffer1 dave.null oldest_to_newest 75963 0 cyril.concolato 2012-10-11 11:11:37 +0000 Bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=17558 describes that --> needs to be banned from the allowed syntax in cue data. However, when XML data is carried in metadata tracks, the XML comments end tag uses the sequence of characters -->. This should be acceptable to a parser, since metadata tracks don't use escapes. 76015 1 ian 2012-10-11 17:28:03 +0000 We don't support XML comments or empty lines in cue payloads. Both cause the parser to assume the cue has ended. 76035 2 silviapfeiffer1 2012-10-11 21:14:20 +0000 I can understand why we wouldn't want to support empty lines. But I think we could tolerate --> if we would only look for the next "-->" after the next empty line. The less restrictions we pose on cue text, the less broken files we will get. 76070 3 zcorpan 2012-10-12 08:20:38 +0000 https://www.w3.org/Bugs/Public/show_bug.cgi?id=14550 76071 4 zcorpan 2012-10-12 08:21:40 +0000 Should we have different parsing rules for metadata tracks? 76156 5 ian 2012-10-12 19:00:55 +0000 You don't know what's a metadata track when parsing. It would be crazy to take a WebVTT file linked to as a metadata cue file, switch it to be a caption file, and suddenly find you had different cues. 76209 6 silviapfeiffer1 2012-10-13 05:15:10 +0000 If we make it dependent on the presence of a "Kind: metadata" marker in the header of the file, we could do that.