- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Thu, 7 Mar 2013 07:28:02 +1100
- To: Ian Hickson <ian@hixie.ch>
- Cc: public-texttracks@w3.org
Received on Wednesday, 6 March 2013 20:28:34 UTC
On 7 Mar 2013 06:53, "Ian Hickson" <ian@hixie.ch> wrote: > > On Mon, 25 Feb 2013, Silvia Pfeiffer wrote: > > > > I was actually wondering about the split and was considering the > > opposite, namely to pull more back into HTML. The TextTrack API and > > TextTrackCue etc should continue to stay in HTML, because you can create > > text tracks and cues without WebVTT. > > Well, the current interface is very WebVTT specific. I could buy splitting > the interface in two, though, with the WebVTT parts in WebVTT and the > generic parts in HTML. Would that work? Yes, that's what I was trying to say. For example the rules for rendering WebVTT cues become the rules for rendering TextTrackCues and then WebVTT can reference them. Is that what you meant? Silvia. > > -- > Ian Hickson U+1047E )\._.,--....,'``. fL > http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. > Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 6 March 2013 20:28:34 UTC