18295 2012-07-18 17:59:46 +0000 <track> data: URLs should be supported 2013-04-23 23:35:10 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED WORKSFORME http://www.whatwg.org/specs/web-apps/current-work/#potentially-cors-enabled-fetch CR P3 normal --- 1 contributor robin mathias mike public-html-admin public-html-wg-issue-tracking robin zcorpan public-html-bugzilla oldest_to_newest 71055 0 contributor 2012-07-18 17:59:46 +0000 This was was cloned from bug 17461 as part of operation convergence. Originally filed: 2012-06-11 10:41:00 +0000 ================================================================================ #0 contributor@whatwg.org 2012-06-11 10:41:00 +0000 -------------------------------------------------------------------------------- Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/fetching-resources.html Multipage: http://www.whatwg.org/C#potentially-cors-enabled-fetch Complete: http://www.whatwg.org/c#potentially-cors-enabled-fetch Comment: <track> data: URLs should be supported Posted from: 2001:4c28:a030:30:450a:b4aa:b818:bf52 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-06-11 10:45:59 +0000 -------------------------------------------------------------------------------- Using <track src="data:...."> currently seems to fail at the "resource sharing check" since there's no Access-Control-Allow-Origin header. To make data: URLs function like same-origin for <track>, I think the potentially CORS-enabled fetch algorithm should have an entry point as "If URL is a data: URL" at the top, and then skip the resource sharing check if URL is a data: URL and instead just set result to success. ================================================================================ 86638 1 robin 2013-04-23 23:35:10 +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: none Rationale: We've already merged the WHATWG change.