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

[Bug 13359] A way is needed to identify the type of data in a track element

From: <bugzilla@jessica.w3.org>
Date: Sat, 20 Aug 2011 06:42:34 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QufGM-0003sL-Ij@jessica.w3.org>

--- Comment #6 from Glenn Adams <glenn@skynav.com> 2011-08-20 06:42:32 UTC ---
(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #3)
> > To expand, consider 3rd party P adding three in-band signaling tracks: IB1 -
> > content advisories for parental control, IB2 - SCTE35 segment descriptors for
> > targeted advertising and IB3 - EISS for interactive television. The user agent
> > executing Page O recognizes these in-band tracks and sources them as three
> > different track elements with kind = metadata as described in [1]. Since the
> > user agent knows how to recognize these in-band tracks it can inform JS of the
> > metadata type by a new TextTrack.type IDL attribute. Without this new
> > attribute, JS will have to contain logic to infer the metadata type, redoing
> > what the UA has already done.
> How would a general-purpose UA (such as Opera, Chrome, Safari or Firefox)
> recognize IB1, IB2, and IB3? They are not specified in HTML so there is no
> requirement for them to be able to decode them and I haven't seen any moves
> that spans across these and other UAs to make IB1-3 a standard-supported format
> in them. If there is, then it would make a lot more sense to have actual
> kind=IB1-3 values as part of the spec IMHO.

There is no requirement that an HTML5 UA decode PNG files, JPEG files, MPEG
video, or even JavaScript or CSS for that matter. So what's the point of your

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 Saturday, 20 August 2011 06:42:36 UTC

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