[html5] r1189 - /

[whatwg at whatwg.org]

Author: ianh
Date: 2008-01-31 21:13:15 -0800 (Thu, 31 Jan 2008)
New Revision: 1189

Modified:
   index
   source
Log:
[e] (1) note canvas v3 ideas, note future requirements when we have bindings-for-dom, note explicitly how forward-compatible getContext() must be

Modified: index
===================================================================
--- index	2008-02-01 02:05:05 UTC (rev 1188)
+++ index	2008-02-01 05:13:15 UTC (rev 1189)
@@ -2160,7 +2160,11 @@
 
   <p>Unless other specified, if a method is passed more arguments than is
    defined for that method in its IDL definition, the excess arguments must
-   be ignored.
+   be ignored.</p>
+  <!-- XXX When updating this spec for
+  Bindings-For-DOM-compliance, also remove or consider the equivalent
+  requirement in the canvas section for toDataURL() and
+  getContext(). -->
 
   <p>Unless other specified, if a method is expecting, as one of its
    arguments, as defined by its IDL definition, an object implementing a
@@ -16087,6 +16091,10 @@
    that it does not support, then it must return null. String comparisons
    must be literal and case-sensitive.
 
+  <p>Arguments other than the <var title="">contextId</var> must be ignored,
+   and must not cause the user agent to raise an exception (as would normally
+   occur if a method was called with the wrong number of arguments).
+
   <p class=note>A future version of this specification will probably define a
    <code>3d</code> context (probably based on the OpenGL ES API).
 
@@ -16319,7 +16327,24 @@
   <p>The <dfn id=restore
    title=dom-context-2d-restore><code>restore()</code></dfn> method must pop
    the top entry in the drawing state stack, and reset the drawing state it
-   describes. If there is no saved state, the method must do nothing.
+   describes. If there is no saved state, the method must do nothing.</p>
+  <!-- XXXv3
+idea from Mihai:
+> 5. Drawing states should be saveable with IDs, and for easier restoring.
+>
+> save(id)
+> restore(id)
+>
+> If id is not provided, then save() works as defined now. The same for
+> restore().
+>
+> Currently, it's not trivial to save and restore a specific state.
+...and from Philip:
+> I think a more convenient syntax would be:
+>   var state = ctx.save();
+>   ctx.restore(state);
+> But how would it interact with normal calls to ctx.restore()?
+  -->
 
   <h6 id=transformations><span class=secno>3.14.11.1.2. </span><dfn
    id=transformations0

Modified: source
===================================================================
--- source	2008-02-01 02:05:05 UTC (rev 1188)
+++ source	2008-02-01 05:13:15 UTC (rev 1189)
@@ -534,7 +534,10 @@
 
   <p>Unless other specified, if a method is passed more arguments than
   is defined for that method in its IDL definition, the excess
-  arguments must be ignored.</p>
+  arguments must be ignored.</p> <!-- XXX When updating this spec for
+  Bindings-For-DOM-compliance, also remove or consider the equivalent
+  requirement in the canvas section for toDataURL() and
+  getContext(). -->
 
   <p>Unless other specified, if a method is expecting, as one of its
   arguments, as defined by its IDL definition, an object implementing
@@ -13637,6 +13640,11 @@
   context that it does not support, then it must return null. String
   comparisons must be literal and case-sensitive.</p>
 
+  <p>Arguments other than the <var title="">contextId</var> must be
+  ignored, and must not cause the user agent to raise an exception (as
+  would normally occur if a method was called with the wrong number of
+  arguments).</p>
+
   <p class="note">A future version of this specification will probably
   define a <code>3d</code> context (probably based on the OpenGL ES
   API).</p>
@@ -13858,7 +13866,25 @@
   drawing state it describes. If there is no saved state, the method
   must do nothing.</p>
 
+  <!-- XXXv3
+idea from Mihai:
+> 5. Drawing states should be saveable with IDs, and for easier restoring.
+>
+> save(id)
+> restore(id)
+>
+> If id is not provided, then save() works as defined now. The same for
+> restore().
+>
+> Currently, it's not trivial to save and restore a specific state.
+...and from Philip:
+> I think a more convenient syntax would be:
+>   var state = ctx.save();
+>   ctx.restore(state);
+> But how would it interact with normal calls to ctx.restore()?
+  -->
 
+
   <h6><dfn title="dom-context-2d-transformation">Transformations</dfn></h6>
 
   <p>The transformation matrix is applied to coordinates when creating