On Mon, 11 Jun 2012 22:53:30 +0200, <[email protected]> wrote:
Author: ianh Date: 2012-06-11 13:53:26 -0700 (Mon, 11 Jun 2012) New Revision: 7128 Modified: complete.html index source Log: [giow] (2) Try to define img synchronous loading. Affected topics: HTML
Modified: source =================================================================== --- source 2012-06-08 21:50:19 UTC (rev 7127) +++ source 2012-06-11 20:53:26 UTC (rev 7128) @@ -25449,6 +25449,19 @@ per CSS inch, and thus if the image data is 300x600, it has an intrinsic dimension of 96 CSS pixels by 192 CSS pixels.</p> + <p>Each <code>Document</code> object must have a <dfn>list of + available images</dfn>. Each image in this list is identified by a + tuple consisting of an <span>absolute URL</span>, a <span>CORS + settings attribute</span> mode, and, if the mode is not <span + title="attr-crossorigin-none">No CORS</span>, an
...
+ <li><p>Let <var title="">key</var> be a tuple consisting of the + resulting <span>absolute URL</span>, the <code>img</code> element's + <code title="attr-crossorigin">crossorigin</code> attribute's mode, + and, if that mode is not <span title="attr-crossorigin-none">No + CORS</span>, the <code>Document</code> object's + <span>origin</span>.</p></li>
The potentially CORS-enabled fetch algorithm ignores the state of the crossorigin attribute when the URL is same-origin. Maybe the sync loading logic needs to align with that behavior.
-- Simon Pieters Opera Software
