- From: Simon Pieters <simonp@opera.com>
- Date: Thu, 22 Jan 2015 08:52:46 +0100
- To: "Loretta Guarino Reid" <lorettaguarino@google.com>
- Cc: "John Foliot" <john@foliot.ca>, "Jeroen Wijering" <jeroen@jwplayer.com>, "David Singer" <singer@apple.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 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
Received on Thursday, 22 January 2015 07:53:24 UTC