[Webkit-unassigned] [Bug 110479] [Meta] Implement support for TTML

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=110479





--- Comment #12 from Silvia Pfeiffer <silviapf at chromium.org>  2013-02-21 19:17:01 PST ---
(In reply to comment #10)
> (In reply to comment #9)
> > I fail to understand how you can represent TTML in the browser without making use of these constructs that <track> stands for.
> 
> Where did I see I wouldn't make use of these constructs?

When you said:

> > > I would not agree with a number of your above statements:
> > > 
> > > * that TTML content needs to be translated into a list of cues (as currently defined)
> > > * that TTML content needs to be mapped to HTML or CSS
> > > * that it is impossible to implement TTML without these clarifications
> > > * that it is impossible to implement TTML compatibly between browsers


> Nothing here requires populating cues. That is, the set of cues could be exposed or not via the DOM.

Are you suggesting to parse a <track> element into a HTMLTrackElement, but not actually giving it a TextTrack object?

Are you further suggesting to "just render" the text on top of the video without adding it to the shadow DOM? How is this rendering supposed to work? Are you intending to render pixels into the video before the video is displayed?

The way in which <track> is specified in HTML5 is that it introduces content into the browser that a JS developer can manipulate. Therefore it populates all of the objects. This is intentional and not a bug.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.