W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2011

[Bug 14241] <track> Merge HTMLTrackElement and TextTrack into one interface

From: <bugzilla@jessica.w3.org>
Date: Thu, 22 Sep 2011 11:58:25 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1R6hv7-0007eB-Gu@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14241

--- Comment #1 from Simon Pieters <simonp@opera.com> 2011-09-22 11:58:24 UTC ---
I think the API could be better if the TextTrack stuff were moved to the
HTMLTrackElement interface and <track> elements are used instead of TextTrack
objects. It's dodgy to have both an element and an object, especially with
events and event handlers:

The spec says to fire 'load' and 'error' on <track> but TextTrack has onload
and onerror handlers (nowhere does the spec say to fire 'load' or 'error' on
TextTrack AFAICT).

The spec says to fire 'cuechange' on both TextTrack and <track>.

(First I considered whether the spec should make <track onload> reflect
TextTrack.onload (like <body onload> reflects window.onload), and only fire the
events on the TextTrack object, but then I wondered why there are two objects
to begin with.)

We don't have an element and an object for audio, video, images, etc. We just
use the element. Should do the same with <track>.

For in-band tracks, you would create <track> elements and associate them with
the <video> without inserting them to the document.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 22 September 2011 11:58:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:04 UTC