[e] (0) Based on feedback about videos on links, give up on giving vi…

…deos activation behaviours. Clean up some conformance criteria in the canvas lines section.

git-svn-id: http://svn.whatwg.org/webapps@3642 340c8d12-0b0e-0410-8428-c7bf67bfef74

index

@@ -20048,21 +20048,7 @@ href="?audio"&gt;audio&lt;/a&gt; test instead.)&lt;/p&gt;</pre>
   it is the intrinsic height of the <a href=#poster-frame>poster frame</a>, if that
   is available; otherwise it is 150 CSS pixels.</p>
 
-  <hr><!-- XXX (awaiting more impl experience)
-   Make the default activation behavior be to do the play() if paused,
-   pause() otherwise?
-   The implementation experience that I am awaiting is basically, does
-   the above make sense? It would mean that the author could bind an
-   access key to the play/pause behaviour, but is that really useful,
-   when the author can just script the whole control if desired? It
-   would mean that if the author called .click() on the element, it
-   would play/pause the element, as well as firing an event. It would
-   also mean that while every other control could be controlled by the
-   user agent (when controls="" is set) and the author (via script),
-   clicking anywhere on the video, whether the element had a
-   controls="" attribute or not, would always play/pause the video.
-   It would also prevent putting a <video> in a link.
-  --><p>User agents should provide controls to enable or disable the
+  <hr><p>User agents should provide controls to enable or disable the
   display of closed captions associated with the video stream, though
   such features should, again, not interfere with the page's normal
   rendering.</p>
@@ -24064,13 +24050,15 @@ idea from Mihai:
 
   <p>The <dfn id=dom-context-2d-linewidth title=dom-context-2d-lineWidth><code>lineWidth</code></dfn>
   attribute gives the width of lines, in coordinate space units. On
-  setting, zero, negative, infinite, and NaN values must be ignored,
-  leaving the value unchanged.</p>
+  getting, it must return the current value. On setting, zero,
+  negative, infinite, and NaN values must be ignored, leaving the
+  value unchanged; other values must change the current value to the
+  new value.</p>
 
   <p>When the context is created, the <code title=dom-context-2d-lineWidth><a href=#dom-context-2d-linewidth>lineWidth</a></code> attribute must
   initially have the value <code>1.0</code>.</p>
 
-  <p>The <dfn id=dom-context-2d-linecap title=dom-context-2d-lineCap><code>lineCap</code></dfn> attribute
+  <hr><p>The <dfn id=dom-context-2d-linecap title=dom-context-2d-lineCap><code>lineCap</code></dfn> attribute
   defines the type of endings that UAs will place on the end of
   lines. The three valid values are <code>butt</code>,
   <code>round</code>, and <code>square</code>. The <code>butt</code>
@@ -24081,28 +24069,32 @@ idea from Mihai:
   the end of the line. The <code>square</code> value means that a
   rectangle with the length of the line width and the width of half
   the line width, placed flat against the edge perpendicular to the
-  direction of the line, must be added at the end of each line. On
-  setting, any other value than the literal strings <code>butt</code>,
-  <code>round</code>, and <code>square</code> must be ignored, leaving
+  direction of the line, must be added at the end of each line.</p>
+
+  <p>On getting, it must return the current value. On setting, if the
+  new value is one of the literal strings <code>butt</code>,
+  <code>round</code>, and <code>square</code>, then the current value
+  must be changed to the new value; other values must ignored, leaving
   the value unchanged.</p>
 
   <p>When the context is created, the <code title=dom-context-2d-lineCap><a href=#dom-context-2d-linecap>lineCap</a></code> attribute must
   initially have the value <code>butt</code>.</p>
 
-
-  <p>The <dfn id=dom-context-2d-linejoin title=dom-context-2d-lineJoin><code>lineJoin</code></dfn>
+  <hr><p>The <dfn id=dom-context-2d-linejoin title=dom-context-2d-lineJoin><code>lineJoin</code></dfn>
   attribute defines the type of corners that UAs will place where two
   lines meet. The three valid values are <code>bevel</code>,
   <code>round</code>, and <code>miter</code>.</p>
 
-  <p>On setting, any other value than the literal strings
-  <code>bevel</code>, <code>round</code>, and <code>miter</code> must
-  be ignored, leaving the value unchanged.</p>
+  <p>On getting, it must return the current value. On setting, if the
+  new value is one of the literal strings <code>bevel</code>,
+  <code>round</code>, and <code>miter</code>, then the current value
+  must be changed to the new value; other values must be ignored,
+  leaving the value unchanged.</p>
 
   <p>When the context is created, the <code title=dom-context-2d-lineJoin><a href=#dom-context-2d-linejoin>lineJoin</a></code> attribute must
   initially have the value <code>miter</code>.</p>
 
-  <p>A join exists at any point in a subpath shared by two consecutive
+  <hr><p>A join exists at any point in a subpath shared by two consecutive
   lines. When a subpath is closed, then a join also exists at its
   first point (equivalent to its last point) connecting the first and
   last lines in the subpath.</p>
@@ -24142,19 +24134,15 @@ idea from Mihai:
   the miter limit ratio to be exceeded, this second triangle must not
   be rendered.</p>
 
-
   <p>The miter limit ratio can be explicitly set using the <dfn id=dom-context-2d-miterlimit title=dom-context-2d-miterLimit><code>miterLimit</code></dfn>
-  attribute. On setting, zero, negative, infinite, and NaN values must
-  be ignored, leaving the value unchanged.</p>
+  attribute. On getting, it must return the current value. On setting,
+  zero, negative, infinite, and NaN values must be ignored, leaving
+  the value unchanged; other values must change the current value to
+  the new value.</p>
 
   <p>When the context is created, the <code title=dom-context-2d-miterLimit><a href=#dom-context-2d-miterlimit>miterLimit</a></code> attribute must
   initially have the value <code>10.0</code>.</p>
 
-
-  <!-- XXX this section doesn't say what these attributes return or
-  what they do on setting. not a big deal; it's pretty obvious. but if
-  anyone complains, we'll have to add it -->
-
   <!--
 v4: dashed lines have been requested. Philip Taylor provides these
 notes on what would need to be defined for dashed lines:

source

@@ -371,7 +371,7 @@
 
   <p class="example">This is an example.</p>
 
-  <p class="XXX">This is an open issue.</p>
+  <p class="&#x0058;&#x0058;&#x0058;">This is an open issue.</p>
 
   <p class="warning">This is a warning.</p>
 
@@ -21518,22 +21518,6 @@ href="?audio">audio&lt;/a> test instead.)&lt;/p></pre>
 
   <hr>
 
-  <!-- XXX (awaiting more impl experience)
-   Make the default activation behavior be to do the play() if paused,
-   pause() otherwise?
-   The implementation experience that I am awaiting is basically, does
-   the above make sense? It would mean that the author could bind an
-   access key to the play/pause behaviour, but is that really useful,
-   when the author can just script the whole control if desired? It
-   would mean that if the author called .click() on the element, it
-   would play/pause the element, as well as firing an event. It would
-   also mean that while every other control could be controlled by the
-   user agent (when controls="" is set) and the author (via script),
-   clicking anywhere on the video, whether the element had a
-   controls="" attribute or not, would always play/pause the video.
-   It would also prevent putting a <video> in a link.
-  -->
-
   <p>User agents should provide controls to enable or disable the
   display of closed captions associated with the video stream, though
   such features should, again, not interfere with the page's normal
@@ -26229,13 +26213,17 @@ idea from Mihai:
   <p>The <dfn
   title="dom-context-2d-lineWidth"><code>lineWidth</code></dfn>
   attribute gives the width of lines, in coordinate space units. On
-  setting, zero, negative, infinite, and NaN values must be ignored,
-  leaving the value unchanged.</p>
+  getting, it must return the current value. On setting, zero,
+  negative, infinite, and NaN values must be ignored, leaving the
+  value unchanged; other values must change the current value to the
+  new value.</p>
 
   <p>When the context is created, the <code
   title="dom-context-2d-lineWidth">lineWidth</code> attribute must
   initially have the value <code>1.0</code>.</p>
 
+  <hr>
+
   <p>The <dfn
   title="dom-context-2d-lineCap"><code>lineCap</code></dfn> attribute
   defines the type of endings that UAs will place on the end of
@@ -26248,30 +26236,38 @@ idea from Mihai:
   the end of the line. The <code>square</code> value means that a
   rectangle with the length of the line width and the width of half
   the line width, placed flat against the edge perpendicular to the
-  direction of the line, must be added at the end of each line. On
-  setting, any other value than the literal strings <code>butt</code>,
-  <code>round</code>, and <code>square</code> must be ignored, leaving
+  direction of the line, must be added at the end of each line.</p>
+
+  <p>On getting, it must return the current value. On setting, if the
+  new value is one of the literal strings <code>butt</code>,
+  <code>round</code>, and <code>square</code>, then the current value
+  must be changed to the new value; other values must ignored, leaving
   the value unchanged.</p>
 
   <p>When the context is created, the <code
   title="dom-context-2d-lineCap">lineCap</code> attribute must
   initially have the value <code>butt</code>.</p>
 
+  <hr>
 
   <p>The <dfn
   title="dom-context-2d-lineJoin"><code>lineJoin</code></dfn>
   attribute defines the type of corners that UAs will place where two
   lines meet. The three valid values are <code>bevel</code>,
   <code>round</code>, and <code>miter</code>.</p>
 
-  <p>On setting, any other value than the literal strings
-  <code>bevel</code>, <code>round</code>, and <code>miter</code> must
-  be ignored, leaving the value unchanged.</p>
+  <p>On getting, it must return the current value. On setting, if the
+  new value is one of the literal strings <code>bevel</code>,
+  <code>round</code>, and <code>miter</code>, then the current value
+  must be changed to the new value; other values must be ignored,
+  leaving the value unchanged.</p>
 
   <p>When the context is created, the <code
   title="dom-context-2d-lineJoin">lineJoin</code> attribute must
   initially have the value <code>miter</code>.</p>
 
+  <hr>
+
   <p>A join exists at any point in a subpath shared by two consecutive
   lines. When a subpath is closed, then a join also exists at its
   first point (equivalent to its last point) connecting the first and
@@ -26313,21 +26309,17 @@ idea from Mihai:
   the miter limit ratio to be exceeded, this second triangle must not
   be rendered.</p>
 
-
   <p>The miter limit ratio can be explicitly set using the <dfn
   title="dom-context-2d-miterLimit"><code>miterLimit</code></dfn>
-  attribute. On setting, zero, negative, infinite, and NaN values must
-  be ignored, leaving the value unchanged.</p>
+  attribute. On getting, it must return the current value. On setting,
+  zero, negative, infinite, and NaN values must be ignored, leaving
+  the value unchanged; other values must change the current value to
+  the new value.</p>
 
   <p>When the context is created, the <code
   title="dom-context-2d-miterLimit">miterLimit</code> attribute must
   initially have the value <code>10.0</code>.</p>
 
-
-  <!-- XXX this section doesn't say what these attributes return or
-  what they do on setting. not a big deal; it's pretty obvious. but if
-  anyone complains, we'll have to add it -->
-
   <!--
 v4: dashed lines have been requested. Philip Taylor provides these
 notes on what would need to be defined for dashed lines: