[html5] r8288 - [giow] (2) imageSmoothingEnabled logic was backwards, oops Fixing https://www.w3 [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2013-11-15 13:26:13 -0800 (Fri, 15 Nov 2013)
New Revision: 8288

Modified:
   complete.html
   index
   source
Log:
[giow] (2) imageSmoothingEnabled logic was backwards, oops
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=23635
Affected topics: Canvas

Modified: complete.html
===================================================================
--- complete.html	2013-11-15 21:20:55 UTC (rev 8287)
+++ complete.html	2013-11-15 21:26:13 UTC (rev 8288)
@@ -56097,7 +56097,7 @@
 
     <p>If the original image data is a bitmap image, the value painted at a point in the area of the
     repetitions is computed by filtering the original image data. When scaling up, if the <code title=dom-context-2d-imageSmoothingEnabled><a href=#dom-context-2d-imagesmoothingenabled>imageSmoothingEnabled</a></code> attribute is set to
-    true, the image must be rendered using nearest-neighbor interpolation. Otherwise, the user agent
+    false, the image must be rendered using nearest-neighbor interpolation. Otherwise, the user agent
     may use any filtering algorithm (for example bilinear interpolation or nearest-neighbor). When
     such a filtering algorithm requires a pixel value from outside the original image data, it must
     instead use the value from wrapping the pixel's coordinates to the original image's dimensions.
@@ -57039,11 +57039,13 @@
     negative. <!-- note: that last sentence has several times been needed to correct people who
     suggested that 5,5,-2,-2 was different than 3,3,2,2 --></p>
 
+<!--CLEANUP-->
     <p>When scaling up, if the <code title=dom-context-2d-imageSmoothingEnabled><a href=#dom-context-2d-imagesmoothingenabled>imageSmoothingEnabled</a></code>
     attribute is set to true, the user agent should attempt to apply a smoothing algorithm to
     the image data when it is scaled. Otherwise, the image must be rendered using nearest-neighbor
     interpolation.</p>
 
+<!--CLEANUP-->
     <p class=note>This specification does not define the precise algorithm to use when scaling an
     image down, or when scaling an image up when the <code title=dom-context-2d-imageSmoothingEnabled><a href=#dom-context-2d-imagesmoothingenabled>imageSmoothingEnabled</a></code>
     attribute is set to true.</p>

Modified: index
===================================================================
--- index	2013-11-15 21:20:55 UTC (rev 8287)
+++ index	2013-11-15 21:26:13 UTC (rev 8288)
@@ -56097,7 +56097,7 @@
 
     <p>If the original image data is a bitmap image, the value painted at a point in the area of the
     repetitions is computed by filtering the original image data. When scaling up, if the <code title=dom-context-2d-imageSmoothingEnabled><a href=#dom-context-2d-imagesmoothingenabled>imageSmoothingEnabled</a></code> attribute is set to
-    true, the image must be rendered using nearest-neighbor interpolation. Otherwise, the user agent
+    false, the image must be rendered using nearest-neighbor interpolation. Otherwise, the user agent
     may use any filtering algorithm (for example bilinear interpolation or nearest-neighbor). When
     such a filtering algorithm requires a pixel value from outside the original image data, it must
     instead use the value from wrapping the pixel's coordinates to the original image's dimensions.
@@ -57039,11 +57039,13 @@
     negative. <!-- note: that last sentence has several times been needed to correct people who
     suggested that 5,5,-2,-2 was different than 3,3,2,2 --></p>
 
+<!--CLEANUP-->
     <p>When scaling up, if the <code title=dom-context-2d-imageSmoothingEnabled><a href=#dom-context-2d-imagesmoothingenabled>imageSmoothingEnabled</a></code>
     attribute is set to true, the user agent should attempt to apply a smoothing algorithm to
     the image data when it is scaled. Otherwise, the image must be rendered using nearest-neighbor
     interpolation.</p>
 
+<!--CLEANUP-->
     <p class=note>This specification does not define the precise algorithm to use when scaling an
     image down, or when scaling an image up when the <code title=dom-context-2d-imageSmoothingEnabled><a href=#dom-context-2d-imagesmoothingenabled>imageSmoothingEnabled</a></code>
     attribute is set to true.</p>

Modified: source
===================================================================
--- source	2013-11-15 21:20:55 UTC (rev 8287)
+++ source	2013-11-15 21:26:13 UTC (rev 8288)
@@ -62273,7 +62273,7 @@
     <p>If the original image data is a bitmap image, the value painted at a point in the area of the
     repetitions is computed by filtering the original image data. When scaling up, if the <code
     data-x="dom-context-2d-imageSmoothingEnabled">imageSmoothingEnabled</code> attribute is set to
-    true, the image must be rendered using nearest-neighbor interpolation. Otherwise, the user agent
+    false, the image must be rendered using nearest-neighbor interpolation. Otherwise, the user agent
     may use any filtering algorithm (for example bilinear interpolation or nearest-neighbor). When
     such a filtering algorithm requires a pixel value from outside the original image data, it must
     instead use the value from wrapping the pixel's coordinates to the original image's dimensions.
@@ -63368,11 +63368,13 @@
     negative. <!-- note: that last sentence has several times been needed to correct people who
     suggested that 5,5,-2,-2 was different than 3,3,2,2 --></p>
 
+<!--CLEANUP-->
     <p>When scaling up, if the <code data-x="dom-context-2d-imageSmoothingEnabled">imageSmoothingEnabled</code>
     attribute is set to true, the user agent should attempt to apply a smoothing algorithm to
     the image data when it is scaled. Otherwise, the image must be rendered using nearest-neighbor
     interpolation.</p>
 
+<!--CLEANUP-->
     <p class="note">This specification does not define the precise algorithm to use when scaling an
     image down, or when scaling an image up when the <code data-x="dom-context-2d-imageSmoothingEnabled">imageSmoothingEnabled</code>
     attribute is set to true.</p>