- From: David Singer <singer@apple.com>
- Date: Mon, 19 Jan 2015 16:53:42 -0500
- To: Jeroen Wijering <jeroen@jwplayer.com>
- Cc: Steve Heffernan <steve@zencoder.com>, John Luther <jluther@jwplayer.com>, Philip Jägenstedt <philipj@opera.com>, "public-texttracks@w3.org" <public-texttracks@w3.org>, rick.eyre@hotmail.com, gkatsevman@brightcove.com
Thank you!! Inline… > On Jan 19, 2015, at 15:39 , Jeroen Wijering <jeroen@jwplayer.com> wrote: > > With JW Player, we implemented basic parsing of cues and rendering of > cues according to the draft spec. Especially in the area of rendering, > the spec is well defined and very helpful to implementors. With TTML > and SRT, we had to be much more creative in doing the rendering. Let > me know what exactly you'd like to see in terms of feedback on the > spec; our player engineers can put that together. > > We have not yet implemented regions. It's a bit hard to comment on the > spec without doing the work; you always find the small details when > implementing. It reads very defined and focused to the use case though > (608 compatibility). If you require comments from people that have > implemented the spec, we could look into prioritizing this work for JW > Player. These two paragraphs are great feedback by themselves! I read it as “we have reviewed and implemented most of the spec. without questions; for regions, we have reviewed and it seems well documented, but have not yet implemented”. Note that if I remember, I’ll get an MPEG liaison saying that we implemented VTT-in-MP4 using the parsing process (to the level needed) directly lifted from the spec., without issues or need for comment. > > The one item I'm missing from the spec is inline CSS, but that's > pushed to V2 right? Sort-of. I think that we can and should develop consensus on how to handle it, and then a question of when it’s integrated into the bleeding-edge whatwg spec. is easy. whether we roll a 1.1 through the Rec process is a separate question. > (https://www.w3.org/Bugs/Public/show_bug.cgi?id=15023) On platforms > like Flash or native Android, we'd like to have all cue styling inline > since there's no CSS. Publisher also need it when converting from > legacy formats (608, TTML) into VTT. In these formats, the styling > also "lives" inline. when you say inline CSS, you mean both of a) style-sheets in the header? b) styling in the cues themselves, using CSS snippets? Have you looked at the old threads on this question? I think we got close to a number of possible designs, but held off until it was really needed and we had real implementers on hand. > > - Jeroen > > > > On Wed, Jan 14, 2015 at 4:40 PM, Steve Heffernan <steve@zencoder.com> wrote: >> I've CC'd Gary Katsevman who's done the most work with the vtt spec for >> Video.js. Gary, how do you feel about the state of the VTT spec? Did you run >> into any issues that could be submitted as a bug? >> >> Also CC'd Rick Eyre (mozilla/vtt.js) though he's probably already on the >> list. >> >> -Steve David Singer Manager, Software Standards, Apple Inc.
Received on Monday, 19 January 2015 21:54:13 UTC