[html5] r6601 - [e] (0) Clarify some implications about getImageData() resolution.

[whatwg at whatwg.org]

Author: ianh
Date: 2011-09-29 16:57:18 -0700 (Thu, 29 Sep 2011)
New Revision: 6601

Modified:
   complete.html
   index
   source
Log:
[e] (0) Clarify some implications about getImageData() resolution.

Modified: complete.html
===================================================================
--- complete.html	2011-09-29 22:30:27 UTC (rev 6600)
+++ complete.html	2011-09-29 23:57:18 UTC (rev 6601)
@@ -37826,6 +37826,11 @@
   for all of the <code title=dom-context-2d-getImageData><a href=#dom-context-2d-getimagedata>createImageData()</a></code>, <code title=dom-context-2d-getImageData><a href=#dom-context-2d-getimagedata>getImageData()</a></code> and <code title=dom-context-2d-putImageData><a href=#dom-context-2d-putimagedata>putImageData()</a></code>
   operations.</p>
 
+  <p class=note>This implies that the data returned by <code title=dom-context-2d-getImageData><a href=#dom-context-2d-getimagedata>getImageData()</a></code> is at the
+  resolution of the canvas backing store. This is likely to not be one
+  device pixel to each CSS pixel if the display used is a high
+  resolution display.</p>
+
   <p class=note>Due to the lossy nature of converting to and from
   premultiplied alpha color values, pixels that have just been set
   using <code title=dom-context-2d-putImageData><a href=#dom-context-2d-putimagedata>putImageData()</a></code> might be
@@ -37841,11 +37846,6 @@
 
   <div class=example>
 
-   <p>The data returned by <code title=dom-context-2d-getImageData><a href=#dom-context-2d-getimagedata>getImageData()</a></code> is at the
-   resolution of the canvas backing store, which is likely to not be
-   one device pixel to each CSS pixel if the display used is a high
-   resolution display.</p>
-
    <p>In the following example, the script generates an
    <code><a href=#imagedata>ImageData</a></code> object so that it can draw onto it.</p>
 

Modified: index
===================================================================
--- index	2011-09-29 22:30:27 UTC (rev 6600)
+++ index	2011-09-29 23:57:18 UTC (rev 6601)
@@ -37693,6 +37693,11 @@
   for all of the <code title=dom-context-2d-getImageData><a href=#dom-context-2d-getimagedata>createImageData()</a></code>, <code title=dom-context-2d-getImageData><a href=#dom-context-2d-getimagedata>getImageData()</a></code> and <code title=dom-context-2d-putImageData><a href=#dom-context-2d-putimagedata>putImageData()</a></code>
   operations.</p>
 
+  <p class=note>This implies that the data returned by <code title=dom-context-2d-getImageData><a href=#dom-context-2d-getimagedata>getImageData()</a></code> is at the
+  resolution of the canvas backing store. This is likely to not be one
+  device pixel to each CSS pixel if the display used is a high
+  resolution display.</p>
+
   <p class=note>Due to the lossy nature of converting to and from
   premultiplied alpha color values, pixels that have just been set
   using <code title=dom-context-2d-putImageData><a href=#dom-context-2d-putimagedata>putImageData()</a></code> might be
@@ -37708,11 +37713,6 @@
 
   <div class=example>
 
-   <p>The data returned by <code title=dom-context-2d-getImageData><a href=#dom-context-2d-getimagedata>getImageData()</a></code> is at the
-   resolution of the canvas backing store, which is likely to not be
-   one device pixel to each CSS pixel if the display used is a high
-   resolution display.</p>
-
    <p>In the following example, the script generates an
    <code><a href=#imagedata>ImageData</a></code> object so that it can draw onto it.</p>
 

Modified: source
===================================================================
--- source	2011-09-29 22:30:27 UTC (rev 6600)
+++ source	2011-09-29 23:57:18 UTC (rev 6601)
@@ -41902,6 +41902,12 @@
   title="dom-context-2d-putImageData">putImageData()</code>
   operations.</p>
 
+  <p class="note">This implies that the data returned by <code
+  title="dom-context-2d-getImageData">getImageData()</code> is at the
+  resolution of the canvas backing store. This is likely to not be one
+  device pixel to each CSS pixel if the display used is a high
+  resolution display.</p>
+
   <p class="note">Due to the lossy nature of converting to and from
   premultiplied alpha color values, pixels that have just been set
   using <code
@@ -41925,12 +41931,6 @@
 
   <div class="example">
 
-   <p>The data returned by <code
-   title="dom-context-2d-getImageData">getImageData()</code> is at the
-   resolution of the canvas backing store, which is likely to not be
-   one device pixel to each CSS pixel if the display used is a high
-   resolution display.</p>
-
    <p>In the following example, the script generates an
    <code>ImageData</code> object so that it can draw onto it.</p>