[giow] (1) Neuter 'currentColor' for addColorStop(), so that we don't…

… have to track around which <canvas> created which CanvasGradient all the time. Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=10023 git-svn-id: http://svn.whatwg.org/webapps@5389 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Aug 28, 2010 · 0256cbf · 0256cbf
1 parent be463cd
commit 0256cbf
Show file tree

Hide file tree

Showing 3 changed files with 41 additions and 0 deletions.
diff --git a/complete.html b/complete.html
@@ -30319,6 +30319,19 @@ <h5 id=2dcontext><span class=secno>4.8.11.1 </span>The 2D context</h5>
   computed value of the <code title="">currentColor</code> keyword is
   fully opaque black. <a href=#refsCSSCOLOR>[CSSCOLOR]</a></p>
 
+  <p>In the case of <code title=dom-canvasgradient-addColorStop><a href=#dom-canvasgradient-addcolorstop>addColorStop()</a></code> on
+  <code><a href=#canvasgradient>CanvasGradient</a></code>, the "computed value of the 'color'
+  property" for the purposes of determining the computed value of the
+  <code title="">currentColor</code> keyword is always fully opaque
+  black (there is no associated element). <a href=#refsCSSCOLOR>[CSSCOLOR]</a></p>
+
+  <p class=note>This is because <code><a href=#canvasgradient>CanvasGradient</a></code> objects
+  are <code><a href=#the-canvas-element>canvas</a></code>-neutral &mdash; a
+  <code><a href=#canvasgradient>CanvasGradient</a></code> object created by one
+  <code><a href=#the-canvas-element>canvas</a></code> can be used by another, and there is therefore
+  no way to know which is the "element in question" at the time that
+  the color is specified.</p>
+
   </div>
 
 

diff --git a/index b/index
@@ -30244,6 +30244,19 @@ interface <dfn id=canvaspixelarray>CanvasPixelArray</dfn> {
   computed value of the <code title="">currentColor</code> keyword is
   fully opaque black. <a href=#refsCSSCOLOR>[CSSCOLOR]</a></p>
 
+  <p>In the case of <code title=dom-canvasgradient-addColorStop><a href=#dom-canvasgradient-addcolorstop>addColorStop()</a></code> on
+  <code><a href=#canvasgradient>CanvasGradient</a></code>, the "computed value of the 'color'
+  property" for the purposes of determining the computed value of the
+  <code title="">currentColor</code> keyword is always fully opaque
+  black (there is no associated element). <a href=#refsCSSCOLOR>[CSSCOLOR]</a></p>
+
+  <p class=note>This is because <code><a href=#canvasgradient>CanvasGradient</a></code> objects
+  are <code><a href=#the-canvas-element>canvas</a></code>-neutral &mdash; a
+  <code><a href=#canvasgradient>CanvasGradient</a></code> object created by one
+  <code><a href=#the-canvas-element>canvas</a></code> can be used by another, and there is therefore
+  no way to know which is the "element in question" at the time that
+  the color is specified.</p>
+
   </div>
 
 

diff --git a/source b/source
@@ -33172,6 +33172,21 @@ interface <dfn>CanvasPixelArray</dfn> {
   computed value of the <code title="">currentColor</code> keyword is
   fully opaque black. <a href="#refsCSSCOLOR">[CSSCOLOR]</a></p>
 
+  <p>In the case of <code
+  title="dom-canvasgradient-addColorStop">addColorStop()</code> on
+  <code>CanvasGradient</code>, the "computed value of the 'color'
+  property" for the purposes of determining the computed value of the
+  <code title="">currentColor</code> keyword is always fully opaque
+  black (there is no associated element). <a
+  href="#refsCSSCOLOR">[CSSCOLOR]</a></p>
+
+  <p class="note">This is because <code>CanvasGradient</code> objects
+  are <code>canvas</code>-neutral &mdash; a
+  <code>CanvasGradient</code> object created by one
+  <code>canvas</code> can be used by another, and there is therefore
+  no way to know which is the "element in question" at the time that
+  the color is specified.</p>
+
   </div>