[Webkit-unassigned] [Bug 57803] Work-in-progress on rendering TextTracks on HTML5 Video

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Apr 4 21:06:56 PDT 2011


--- Comment #4 from Dimitri Glazkov (Google) <dglazkov at chromium.org>  2011-04-04 21:06:56 PST ---
No worries. I realize this is a snapshot of your checkout :)

I read up on <track> element and now realize that this is the same use case as the <details>/<summary> element (http://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#the-details-element)

The approach you are currently taking (and the one I misled you toward) is workable, but ultimately is drenched with angel tears and droplets of unicorn blood. The problem here is that the <track> element itself is just data -- it's appearance is projecte onto the visual surface of the video element via MediaControlTextTrackElement. This means we have to manage lifetimes and lifecycles of both of these and synchronize them, and surely suffer through mysterious crashes and bugs all around.

Instead, we should take this approach:

1) Fix bug 56973, which would allow us to place <track> element's render object inside of the RenderVideo hierarchy
2) Implement <track> element as a box (probably a RenderBlock subclass), which displays just the right text inside of it.
3) Profit on a horse.

We are sprinting toward fixing bug 56973, so that we can get this done soon. Can you guys try to land other bits of the track stuff first and hang tight on implementing the visual parts of <track>? We promise to help with advice/code/reviews.


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

More information about the webkit-unassigned mailing list