15836 2012-02-02 00:16:18 +0000 Missing xref placeholder for "split a string on spaces" in WebVTT 2012-10-09 19:10:22 +0000 1 1 1 Unclassified TextTracks CG WebVTT unspecified PC All RESOLVED FIXED P2 normal --- 1 silviapfeiffer1 ian eric.carlson glenn ian mike philipj public-texttracks dave.null oldest_to_newest 63558 0 silviapfeiffer1 2012-02-02 00:16:18 +0000 WebKit have implemented tolerating whitespace on the cue setting such that spaces between cue names and values (behind the colon) are ignored. Basically, in http://dev.w3.org/html5/webvtt/#parse-the-webvtt-settings between steps 2 and 3 there is a "skip whitespace" (except that we now can't leave step 1 as is any more and have to do explicit parsing string by string). Should this be a WebKit bug or should we be more generous in the spec? 63589 1 zcorpan 2012-02-02 08:29:33 +0000 I agree. It's natural to type a space after a colon. Many do it in CSS and JS where it is tolerated. I think I have reported this before, but I can't find it right now (though I found annevk asking for this also in IRC). IIRC, Hixie WONTFIXed my suggestion because he wanted settings to be whitespace-*separated*. I don't understand why that is desirable, and would rather support a syntax that authors write naturally. I'm OK with not skipping whitespace before the colon, but I'd also be OK with doing that. 67065 2 ian 2012-04-25 21:48:59 +0000 These settings are, as Simon says, space-separated tokens. If you put a space after the colon, then it's a separate token. This isn't like CSS; in CSS, properties are semi-colon separated. It's not like JS; in JS, fields are comma-separated. Here, they are space-separated. 67206 3 silviapfeiffer1 2012-04-30 23:50:05 +0000 OK, apparently WebKit is actually parsing it exactly as you say. However, at http://dev.w3.org/html5/webvtt/#parse-the-webvtt-settings we have the sentence "splitting input on spaces" (which incidentally is not linking anywhere but has a green underline). There is nothing actually describing what that means. It should likely accept both spaces and horizontal tabs as separators. Webkit in fact tolerates an infinite number of ' ' and '\t' as separators. 67208 4 glenn 2012-05-01 00:02:11 +0000 (In reply to comment #3) > However, at http://dev.w3.org/html5/webvtt/#parse-the-webvtt-settings we have > the sentence "splitting input on spaces" (which incidentally is not linking > anywhere but has a green underline). There is nothing actually describing what > that means. It should likely accept both spaces and horizontal tabs as > separators. Webkit in fact tolerates an infinite number of ' ' and '\t' as > separators. That's http://dev.w3.org/html5/spec/single-page.html#split-a-string-on-spaces. I think this is missing from 2.1. 67209 5 silviapfeiffer1 2012-05-01 00:04:46 +0000 OK, let's fix this link then. 71358 6 ian 2012-07-24 05:58:02 +0000 I really wish we hadn't pulled this stuff out of the HTML spec where it belongs, it's just going to keep causing these problems. But yeah, I'll add that <dfn> to 2.1. 75719 7 contributor 2012-10-09 19:10:22 +0000 Checked in as WHATWG revision r7445. Check-in comment: Fix some cross-reference issues. http://html5.org/tools/web-apps-tracker?from=7444&to=7445