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

[Bug 12544] <video> MEDIA CONTROLLER requires track kind for in-band tracks

From: <bugzilla@jessica.w3.org>
Date: Thu, 09 Feb 2012 20:39:47 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RvamR-0003Ea-L1@jessica.w3.org>

Bob Lund <b.lund@cablelabs.com> changed:

           What    |Removed                     |Added
                 CC|                            |b.lund@cablelabs.com

--- Comment #25 from Bob Lund <b.lund@cablelabs.com> 2012-02-09 20:39:40 UTC ---

(In reply to comment #24)
> Mark: That would make the API maddeningly hard to use right.
> EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
> satisfied with this response, please change the state of this bug to CLOSED. If
> you have additional information and would like the editor to reconsider, please
> reopen this bug. If you would like to escalate the issue to the full HTML
> Working Group, please add the TrackerRequest keyword to this bug, and suggest
> title and text for the tracker issue; or you may create a tracker issue
> yourself, if you are able to do so. For more details, see this document:
>    http://dev.w3.org/html5/decision-policy/decision-policy.html
> Status: Accepted
> Change Description: see diff given below
> Rationale:
> I've tried to map the most useful DASH role combinations to the defined HTML
> values. Hopefully that's good enough for most purposes. If there are specific
> use cases that this doesn't handle, please file separate bugs (I don't mind if
> they are handled as LC1 bugs).
> If there are other specifications that define specific roles that should be
> mapped here, please file separate bugs with links to the relevant specs (I
> don't mind if they are handled as LC1 bugs either).

I agree that an enumeration of track kinds is best but there is an issue of
spec timing that should be considered.

I raised the need for a new role value with the DASH spec authors to address
the same issue identified in bug 13357 (new kind for pre-mixed audio
descriptions) . The response was that future specs should create new schemes
that define needed Role values.

If Roles (or Role combinations) are _only_ explicitly enumerated in HTML for a
given set of referenced specs then it seems likely there will be  future cases
that aren't captured in a particular version of HTML. It would be very useful
if when the UA encountered a Role, or set of Role values, that were not mapped
in HTML, a string, such as was suggested in Comment 22, was created.

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 Thursday, 9 February 2012 20:39:49 UTC

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