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

[bugzilla-daemon at webkit.org]

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





--- Comment #15 from Silvia Pfeiffer <silviapf at chromium.org>  2013-02-21 20:47:14 PST ---
(In reply to comment #14)
> > > 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.
> > 
> > Sure. But there is nothing in the HTML5 spec that says that cues (or what might be considered a "cue") *must* be exposed and can't be implicitly presented or otherwise processed without exposing actual cue objects. At least there is nothing I'm aware of that mandates this. Please correct me if I've missed it.
> 
> I think you've missed it. Try implementing TTML support and you'll certainly come across it.

I should have been more precise and pointed you to the part that explains how to render cues:
http://www.w3.org/TR/html5/single-page.html#text-track-model

It states:
A text track consists of:
...
A list of zero or more cues:

* A list of text track cues, along with rules for updating the text track rendering. For example, for WebVTT, the rules for updating the display of WebVTT text tracks. [WEBVTT]

* The list of cues of a text track can change dynamically, either because the text track has not yet been loaded or is still loading, or due to DOM manipulation.

Without a list of text track cues and rules for updating the text track rendering there is no display of cues.

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