18216 2012-07-18 17:42:51 +0000 <track> should not load without a media element parent 2013-06-06 07:39:17 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#sourcing-out-of-band-text-tracks CR P3 normal --- 1 contributor silviapfeiffer1 mike odinho public-html-admin public-html-wg-issue-tracking robin zcorpan public-html-bugzilla oldest_to_newest 70898 0 contributor 2012-07-18 17:42:51 +0000 This was was cloned from bug 17271 as part of operation convergence. Originally filed: 2012-05-31 12:52:00 +0000 ================================================================================ #0 contributor@whatwg.org 2012-05-31 12:52:32 +0000 -------------------------------------------------------------------------------- Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html Multipage: http://www.whatwg.org/C#sourcing-out-of-band-text-tracks Complete: http://www.whatwg.org/c#sourcing-out-of-band-text-tracks Comment: <track> Move crossorigin="" to <track> Posted from: 2001:4c28:a030:30:10c4:66a0:3c62:e586 by simonp@opera.com User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.7.3; U; en) Presto/2.10.229 Version/11.64 ================================================================================ #1 Simon Pieters 2012-05-31 12:56:31 +0000 -------------------------------------------------------------------------------- [[ If URL is not the empty string, perform a potentially CORS-enabled fetch of URL, with the mode being the state of the media element's crossorigin content attribute, the origin being the origin of the media element's Document, and the default origin behaviour set to fail. ]] I think this is problematic for several reasons: * There might not be a media element. * You might want to allow cross-origin fetching of the video but not of the tracks, or vice versa. I think it would be better to have a crossorigin attribute on <track> and let the track load algorithm look only at that. ================================================================================ #2 Simon Pieters 2012-06-01 16:12:22 +0000 -------------------------------------------------------------------------------- We discussed this for a bit internally and concluded that the added flexibility with <track crossorigin> was not worth the added verbosity. To solve this: > * There might not be a media element. We suggest instead that <track> never loads if it doesn't have a media element as parent. ================================================================================ 88811 1 silviapfeiffer1 2013-06-06 07:39:17 +0000 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: https://github.com/w3c/html/commit/15de2b08 Rationale: Accepted WHATWG resolution