- From: Philip Jägenstedt <philipj@opera.com>
- Date: Wed, 25 Feb 2015 11:51:07 +0700
- To: David Singer <singer@apple.com>
- Cc: Silvia Pfieffer <silviapfeiffer1@gmail.com>, Jeroen Wijering <jeroen@jwplayer.com>, Steve Heffernan <steve@zencoder.com>, John Luther <jluther@jwplayer.com>, "public-texttracks@w3.org" <public-texttracks@w3.org>, Richard Eyre <rick.eyre@hotmail.com>, Gary Katsevman <gkatsevman@brightcove.com>
On Tue, Feb 24, 2015 at 2:46 AM, David Singer <singer@apple.com> wrote: > >> On Feb 21, 2015, at 23:10 , Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote: >> >> Note that I have made a new suggestion as to how to deal with inline >> styles in VTT. >> https://www.w3.org/Bugs/Public/show_bug.cgi?id=15023#c15 >> >> If that is agreeable and it is a requirement to be added before we go >> to CR, I can write the spec for that (assuming Philip agrees with the >> proposed approach). > > we had a long discussion on this several years back. I’ll try to resurrect the questions > > 1) can new styles occur only in the header, or throughout the file? > I commented on the bug: currently VTT files are beautifully incremental and random accessible; allowing styles to occur anywhere and persist to end of file would badly impact that. Can we do the 90%+ case and have styles only at the beginning, please? I don’t mind if they are ‘part of’ the header or just after it and before the first cue. I don't have a use case for allowing style anywhere and don't know if it matters, but what problem are you trying to avoid? Is it that a file is slow to parse so that the style is parsed and applied too late? Note that cues with early timestamps can be at the end of the file, so it's already possible to author a file poorly. I thought that loading text tracks would block playback start, but I actually can't find that in the HTML spec now. If that were the case, there would be no problem. > 2) What about multi-line? We either need a syntax that allows blank lines, or an escape for them. Years back, we suggested escape. But removing blank lines is as easy as escaping them, and has the huge advantage that the result is still valid CSS. Simon had an interesting idea in https://www.w3.org/Bugs/Public/show_bug.cgi?id=15023#c19 But unless we think this is going to be a big problem, simply not allowing blank lines seems like a good enough start to me. Philip
Received on Wednesday, 25 February 2015 04:51:34 UTC