- From: David Singer <singer@apple.com>
- Date: Tue, 10 Dec 2013 11:34:32 -0800
- To: Glenn Adams <glenn@chromium.org>
- Cc: John Luther <jluther@google.com>, Silvia Pfieffer <silviapfeiffer1@gmail.com>, Victor Cărbune <vcarbune@chromium.org>, Silvia Pfeiffer <silviapf@chromium.org>, "public-texttracks@w3.org" <public-texttracks@w3.org>, Nigel Megitt <nigel.megitt@bbc.co.uk>
On Dec 9, 2013, at 11:36 , Glenn Adams <glenn@chromium.org> wrote: > But not as well as you could it would seem: on Chrome, WebVTT is simply translated to cues referring to a CSS styled HTML fragment. Why not simple define an HTMLCue, and dispense entirely with VTTCue and the WebVTT parser. The WebVTT could be translated to a sequence of HTML cues on the server or using client JS. > This is probably stating the obvious, but you asked. for at least two reasons: * we want this to be only one of many possible implementation choice and * we want there to be a simple expression of the timed cues that is not dependent on an implementation choice David Singer Multimedia and Software Standards, Apple Inc.
Received on Tuesday, 10 December 2013 19:35:00 UTC