[html5] r7164 - [giow] (2) Fix a couple of places that misinvoked the default activation behavio [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2012-06-29 16:20:43 -0700 (Fri, 29 Jun 2012)
New Revision: 7164

Modified:
   complete.html
   index
   source
Log:
[giow] (2) Fix a couple of places that misinvoked the default activation behaviour.
Affected topics: HTML

Modified: complete.html
===================================================================
--- complete.html	2012-06-29 21:35:49 UTC (rev 7163)
+++ complete.html	2012-06-29 23:20:43 UTC (rev 7164)
@@ -55286,8 +55286,10 @@
   <p>If the platform supports letting the user submit a form
   implicitly (for example, on some platforms hitting the "enter" key
   while a text field is focused implicitly submits the form), then
-  doing so must cause the form's <a href=#default-button>default button</a>'s
-  <a href=#activation-behavior>activation behavior</a>, if any, to be run.</p>
+  doing so for a form whose <a href=#default-button>default button</a> has a defined
+  <a href=#activation-behavior>activation behavior</a> must cause the user agent to
+  <a href=#run-synthetic-click-activation-steps>run synthetic click activation steps</a> on that
+  <a href=#default-button>default button</a>.</p>
 
   <p class=note>Consequently, if the <a href=#default-button>default button</a> is
   <a href=#concept-fe-disabled title=concept-fe-disabled>disabled</a>, the form is not
@@ -57396,7 +57398,11 @@
   of the command is always false. (The command is never checked.)</p>
 
   <p>The <a href=#command-facet-action title=command-facet-Action>Action</a> of the
-  command is to <a href=#fire-a-click-event title="fire a click event">fire a <code title=event-click>click</code> event</a> at the element.</p>
+  command, if the element has a defined <a href=#activation-behavior>activation
+  behavior</a>, is to <a href=#run-synthetic-click-activation-steps>run synthetic click activation
+  steps</a> on the element. Otherwise, it is just to <a href=#fire-a-click-event>fire a
+  <code title=event-click>click</code> event</a> at the
+  element.</p>
 
 
   <h5 id=using-the-button-element-to-define-a-command><span class=secno>4.11.5.2 </span><dfn title=button-command>Using the <code>button</code> element to define a command</dfn></h5>

Modified: index
===================================================================
--- index	2012-06-29 21:35:49 UTC (rev 7163)
+++ index	2012-06-29 23:20:43 UTC (rev 7164)
@@ -55286,8 +55286,10 @@
   <p>If the platform supports letting the user submit a form
   implicitly (for example, on some platforms hitting the "enter" key
   while a text field is focused implicitly submits the form), then
-  doing so must cause the form's <a href=#default-button>default button</a>'s
-  <a href=#activation-behavior>activation behavior</a>, if any, to be run.</p>
+  doing so for a form whose <a href=#default-button>default button</a> has a defined
+  <a href=#activation-behavior>activation behavior</a> must cause the user agent to
+  <a href=#run-synthetic-click-activation-steps>run synthetic click activation steps</a> on that
+  <a href=#default-button>default button</a>.</p>
 
   <p class=note>Consequently, if the <a href=#default-button>default button</a> is
   <a href=#concept-fe-disabled title=concept-fe-disabled>disabled</a>, the form is not
@@ -57396,7 +57398,11 @@
   of the command is always false. (The command is never checked.)</p>
 
   <p>The <a href=#command-facet-action title=command-facet-Action>Action</a> of the
-  command is to <a href=#fire-a-click-event title="fire a click event">fire a <code title=event-click>click</code> event</a> at the element.</p>
+  command, if the element has a defined <a href=#activation-behavior>activation
+  behavior</a>, is to <a href=#run-synthetic-click-activation-steps>run synthetic click activation
+  steps</a> on the element. Otherwise, it is just to <a href=#fire-a-click-event>fire a
+  <code title=event-click>click</code> event</a> at the
+  element.</p>
 
 
   <h5 id=using-the-button-element-to-define-a-command><span class=secno>4.11.5.2 </span><dfn title=button-command>Using the <code>button</code> element to define a command</dfn></h5>

Modified: source
===================================================================
--- source	2012-06-29 21:35:49 UTC (rev 7163)
+++ source	2012-06-29 23:20:43 UTC (rev 7164)
@@ -64552,8 +64552,10 @@
   <p>If the platform supports letting the user submit a form
   implicitly (for example, on some platforms hitting the "enter" key
   while a text field is focused implicitly submits the form), then
-  doing so must cause the form's <span>default button</span>'s
-  <span>activation behavior</span>, if any, to be run.</p>
+  doing so for a form whose <span>default button</span> has a defined
+  <span>activation behavior</span> must cause the user agent to
+  <span>run synthetic click activation steps</span> on that
+  <span>default button</span>.</p>
 
   <p class="note">Consequently, if the <span>default button</span> is
   <span title="concept-fe-disabled">disabled</span>, the form is not
@@ -67088,8 +67090,11 @@
   of the command is always false. (The command is never checked.)</p>
 
   <p>The <span title="command-facet-Action">Action</span> of the
-  command is to <span title="fire a click event">fire a <code
-  title="event-click">click</code> event</span> at the element.</p>
+  command, if the element has a defined <span>activation
+  behavior</span>, is to <span>run synthetic click activation
+  steps</span> on the element. Otherwise, it is just to <span>fire a
+  <code title="event-click">click</code> event</span> at the
+  element.</p>
 
 
   <h5><dfn title="button-command">Using the <code>button</code> element to define a command</dfn></h5>