[html5] r1755 - /
whatwg at whatwg.org
whatwg at whatwg.org
Thu Jun 12 16:10:34 PDT 2008
Author: ianh
Date: 2008-06-12 16:10:34 -0700 (Thu, 12 Jun 2008)
New Revision: 1755
Modified:
index
source
Log:
[e] (0) make the intro paragraph easier to understand
Modified: index
===================================================================
--- index 2008-06-12 23:09:52 UTC (rev 1754)
+++ index 2008-06-12 23:10:34 UTC (rev 1755)
@@ -20600,8 +20600,9 @@
href="#canvas">canvas</a></code> elements</h5>
<p><strong>Information leakage</strong> can occur if scripts from one <a
- href="#origin0">origin</a> are exposed to images from another origin (one
- that isn't the <a href="#same-origin" title="same origin">same</a>).
+ href="#origin0">origin</a> can access information (e.g. read pixels) from
+ images from another origin (one that isn't the <a href="#same-origin"
+ title="same origin">same</a>).
<p>To mitigate this, <code><a href="#canvas">canvas</a></code> elements are
defined to have a flag indicating whether they are <i>origin-clean</i>.
Modified: source
===================================================================
--- source 2008-06-12 23:09:52 UTC (rev 1754)
+++ source 2008-06-12 23:10:34 UTC (rev 1755)
@@ -18271,8 +18271,9 @@
<h5>Security with <code>canvas</code> elements</h5>
<p><strong>Information leakage</strong> can occur if scripts from
- one <span>origin</span> are exposed to images from another origin
- (one that isn't the <span title="same origin">same</span>).</p>
+ one <span>origin</span> can access information (e.g. read pixels)
+ from images from another origin (one that isn't the <span
+ title="same origin">same</span>).</p>
<p>To mitigate this, <code>canvas</code> elements are defined to
have a flag indicating whether they are <i>origin-clean</i>. All
More information about the Commit-Watchers
mailing list