- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Fri, 8 Mar 2013 16:44:19 +1100
- To: Ian Hickson <ian@hixie.ch>
- Cc: public-texttracks@w3.org
- Message-ID: <CAHp8n2k6+BgKDVbMts6QQ6uyyn5MiZVF+vy49q2Wauvs-3iFPw@mail.gmail.com>
On Fri, Mar 8, 2013 at 4:55 AM, Ian Hickson <ian@hixie.ch> wrote: > On Thu, 7 Mar 2013, Silvia Pfeiffer wrote: > > On 7 Mar 2013 07:53, "Ian Hickson" <ian@hixie.ch> wrote: > > > On Thu, 7 Mar 2013, Silvia Pfeiffer wrote: > > > > 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? > > > > > > I meant more the other way around. The rules for rendering WebVTT cues > > > are specific to WebVTT (e.g. you wouldn't use them for TTML), and so > > > all the bits on TextTrackCue relating to them, e.g. snapToLines, are > > > WebVTT- specific as well. So I would propose splitting TextTrackCue in > > > half, with WebVTT having a WebVTTTextTrackCue that inherits from > > > TextTrackCue and contains all the WebVTT-specific bits, leaving only > > > the generic format-agnostic stuff (that is as useful for WebVTT as any > > > other text track format) in HTML. > > > > The rules for rendering WebVTT cues are also currently used to render > > the text in TextTrackCue created by JS. Are you suggesting to simplify > > them for TextTrackCue? (Which incidentally I'd be fine with.) > > That's just creating WebVTT cues from JS. Right now, yes, and that's how browsers implement it. > I would move the constructor to > WebVTTCue, so that the hiearachy is: > > EventTarget > | > TextTrackCue -----------------------+ > | | > WebVTTCue (has constructor) FooTTCue (has constructor) > > ...where "FooTT" is some other text track format. > Would TextTrackCue also have a constructor? I.e. do we have a generic text track cue format? Silvia.
Received on Friday, 8 March 2013 05:45:07 UTC