This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 18257 - <track> The UA-defined label should not be exposed in the DOM API. DOM API should see the empty string instead.
Summary: <track> The UA-defined label should not be exposed in the DOM API. DOM API sh...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 17:51 UTC by contributor
Modified: 2012-09-07 19:25 UTC (History)
6 users (show)

See Also:


Attachments

Description contributor 2012-07-18 17:51:42 UTC
This was was cloned from bug 15951 as part of operation convergence.
Originally filed: 2012-02-10 13:14:00 +0000

================================================================================
 #0   contributor@whatwg.org                          2012-02-10 13:14:34 +0000 
--------------------------------------------------------------------------------
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html
Multipage: http://www.whatwg.org/C#dom-texttrack-label
Complete: http://www.whatwg.org/c#dom-texttrack-label

Comment:
The UA-defined label should not be exposed in the DOM API. DOM API should see
the empty string instead.

Posted from: 85.227.157.105 by simonp@opera.com
User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.7.2; U; en) Presto/2.10.229 Version/11.61
================================================================================
 #1   Ian 'Hixie' Hickson                             2012-04-25 18:52:38 +0000 
--------------------------------------------------------------------------------
In principle I agree, but the idea here is that a scripted controller can expose the tracks the same way as the UA controller. Do we really want to require that scripted controllers implement all the label magic?
================================================================================
 #2   Simon Pieters                                   2012-04-25 19:19:36 +0000 
--------------------------------------------------------------------------------
I think sites using custom controls would want to implement their own magic, and using the empty string would provide them with a sane check for when they should use their own magic.
================================================================================
 #3   contributor@whatwg.org                          2012-06-27 21:23:29 +0000 
--------------------------------------------------------------------------------
Checked in as WHATWG revision r7149.
Check-in comment: Make TextTrack.label not expose the UA-specific label if one is being used.
http://html5.org/tools/web-apps-tracker?from=7148&to=7149
================================================================================
 #4   Ian 'Hixie' Hickson                             2012-06-27 21:53:50 +0000 
--------------------------------------------------------------------------------
(reopened pending decision on what to do with bugs that affect the HTMLWG spec)
================================================================================
Comment 1 Silvia Pfeiffer 2012-09-07 19:25:00 UTC
    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: Merged from WHATWG change https://github.com/w3c/html/commit/4886ebc76b0335ceb8e47d2fa8c10868fc6b0be0