W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > February 2012

[Bug 15606] <track> clarification of TextTrackCue.getCueAsHTML() conversion rules

From: <bugzilla@jessica.w3.org>
Date: Wed, 08 Feb 2012 14:47:42 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Rv8oA-0005Mw-T1@jessica.w3.org>

--- Comment #5 from Glenn Adams <glenn@skynav.com> 2012-02-08 14:47:41 UTC ---
(In reply to comment #4)
> (In reply to comment #3)
> > i'd like normative text regarding what should be returned by getCueAsHTML() in
> > the case that the UA does not know the format or does not support conversion of
> > a known format; i would suggest that null be returned in such cases
> If the UA doesn't know the format at all, why would it expose the track in the
> first place? It seems that anything that has a text representation can be
> serialized, and anything else shouldn't be a TextTrackCue at all.

that's a good point (about not exposing a possible text track if the format is
not known or supported); perhaps there should be normative language to that

regarding exposing raw non-text formats, at least one mapping from binary
metadata content to a (base64) text representation in a text track cue has been
defined at:


so it would not do to prohibit exposing binary track data via text track cues;
note that a mapping from CEA-608 or CEA-708 closed caption data (also binary)
into text track cues is likely to be defined at some point;

Configure bugmail: https://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 Wednesday, 8 February 2012 14:49:37 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:26 UTC