On Wed, Dec 11, 2013 at 3:34 AM, David Singer <singer@apple.com> wrote: > > 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 > Which would require the "simple expression" to be a semantic/stylistic superset of formats, which HTML/CSS is, but WebVTT isn't. > > David Singer > Multimedia and Software Standards, Apple Inc. > >
Received on Tuesday, 10 December 2013 20:56:41 UTC