- From: David Singer <singer@apple.com>
- Date: Thu, 22 Jan 2015 10:59:41 -0500
- To: Loretta Guarino Reid <lorettaguarino@google.com>
- Cc: Simon Pieters <simonp@opera.com>, John Foliot <john@foliot.ca>, Jeroen Wijering <jeroen@jwplayer.com>, Steve Heffernan <steve@zencoder.com>, John Luther <jluther@jwplayer.com>, Philip Jägenstedt <philipj@opera.com>, "public-texttracks@w3.org" <public-texttracks@w3.org>, Richard Eyre <rick.eyre@hotmail.com>, Gary Katsevman <gkatsevman@brightcove.com>
> On Jan 22, 2015, at 9:47 , Loretta Guarino Reid <lorettaguarino@google.com> wrote: > > Thanks for the clarification. I agree, inline stylesheets should be sufficient. that was always my ‘high nail’ too (if you look at the old thread). I’ll see if I can excavate where we got to before we got tired of discussion! > > On Wed, Jan 21, 2015 at 11:52 PM, Simon Pieters <simonp@opera.com> wrote: > On Thu, 22 Jan 2015 07:16:42 +0100, Loretta Guarino Reid <lorettaguarino@google.com> wrote: > > In short, style rules in the header of a VTT file is what we (our > publishers) would like to have. Styling rules inside the cues and > links to external CSS are less relevant. > > > CSS can link to external CSS with @import, so VTT doesn't need a dedicated > mechanism for that. > > > This does not solve the problem of keeping all of the authored information > in a single file. I agree with Jeroen on the desirability of style rules in > the header. > > Yes, but I think you missed my point. My point is that if we add a mechanism to include an inline stylesheet, we also get a mechanism to point to an external stylesheet for free, since CSS already has it. > > > -- > Simon Pieters > Opera Software > David Singer Manager, Software Standards, Apple Inc.
Received on Thursday, 22 January 2015 16:00:31 UTC