21505 2013-04-02 08:57:06 +0000 This algorithm does not work well for data URLs. The origin of a data URL resource is a unique identifier. That seems broken for data URLs found in the same document. 2013-05-30 22:05:59 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#downloading-resources P3 normal Unsorted 1 contributor ian annevk ian mike contributor oldest_to_newest 85363 0 contributor 2013-04-02 08:57:06 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#downloading-resources Complete: http://www.whatwg.org/c#downloading-resources Comment: This algorithm does not work well for data URLs. The origin of a data URL resource is a unique identifier. That seems broken for data URLs found in the same document. Posted from: 207.218.72.65 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.6 Safari/537.36 85806 1 ian 2013-04-09 17:56:05 +0000 The fix here is to make the step that says "Let resource origin be the origin of the resource being downloaded" instead say that /resource origin/ is the origin of the resource's URL, unless its scheme is data:, in which case it's the same as interface origin. (And move the step that defines 'interface origin' up so we can refer to it.) Right? 85859 2 annevk 2013-04-10 10:55:25 +0000 Yes, I think for now that is fine. In the future this can use the resource's CORS-same-origin vs CORS-cross-origin flag as the former will be set for data URL downloads. 88474 3 contributor 2013-05-30 22:05:59 +0000 Checked in as WHATWG revision r7873. Check-in comment: Allow data: URLs to be given download='' attribute names. http://html5.org/tools/web-apps-tracker?from=7872&to=7873