- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 17 Jun 2009 05:34:59 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv24279
Modified Files:
Overview.html
Log Message:
Fold command.click() into the regular HTMLElement.click(). (whatwg r3298)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2444
retrieving revision 1.2445
diff -u -d -r1.2444 -r1.2445
--- Overview.html 17 Jun 2009 05:22:57 -0000 1.2444
+++ Overview.html 17 Jun 2009 05:34:56 -0000 1.2445
@@ -7163,6 +7163,10 @@
events dispatched by author script. However, the <code title="dom-click"><a href="#dom-click">click()</a></code> method can be used to make it
happen programmatically.</p>
+ <p>When a user agent is to <dfn id="run-pre-click-activation-steps">run pre-click activation steps</dfn>
+ on an element, it must run the <dfn id="pre-click-activation-steps">pre-click activation steps</dfn>
+ defined for that element, if any.</p>
+
<p>When a user agent is to <dfn id="run-post-click-activation-steps">run post-click activation
steps</dfn> on an element, the user agent must <a href="#fire-a-simple-event">fire a simple
event</a> called <code title="event-DOMActivate">DOMActivate</code> that is cancelable at
@@ -7171,10 +7175,6 @@
canceled, the user agent must <a href="#run-canceled-activation-steps">run canceled activation
steps</a> on the element instead.</p>
- <p>When a user agent is to <dfn id="run-pre-click-activation-steps">run pre-click activation steps</dfn>
- on an element, it must run the <dfn id="pre-click-activation-steps">pre-click activation steps</dfn>
- defined for that element, if any.</p>
-
<p>When a user agent is to <dfn id="run-canceled-activation-steps">run canceled activation steps</dfn>
on an element, it must run the <dfn id="canceled-activation-steps">canceled activation steps</dfn>
defined for that element, if any.</p>
@@ -34024,7 +34024,6 @@
attribute boolean <a href="#dom-command-checked" title="dom-command-checked">checked</a>;
attribute DOMString <a href="#dom-command-radiogroup" title="dom-command-radiogroup">radiogroup</a>;<!--
attribute boolean <span title="dom-command-default">default</span>;-->
- void <a href="#dom-command-click" title="dom-command-click">click</a>(); // shadows <code><a href="#htmlelement">HTMLElement</a></code>.<code title="dom-click"><a href="#dom-click">click()</a></code>
};</pre>
</dd>
</dl><p>The <code><a href="#the-command">command</a></code> element represents a command that the user
@@ -34108,11 +34107,9 @@
DOM attributes must <a href="#reflect">reflect</a> the respective content
attributes of the same name.</p>
- <p>The <dfn id="dom-command-click" title="dom-command-click"><code>click()</code></dfn>
- method's behavior depends on the value of the <code title="attr-command-type"><a href="#attr-command-type">type</a></code> attribute of the element, as
- follows:</p>
-
- <!-- XXX should integrate this better with the normal click() method -->
+ <p>The element's <a href="#activation-behavior">activation behavior</a> depends on the
+ value of the <code title="attr-command-type"><a href="#attr-command-type">type</a></code> attribute
+ of the element, as follows:</p>
<dl class="switch"><dt>If the <code title="attr-command-type"><a href="#attr-command-type">type</a></code> attribute is
in the <a href="#attr-command-type-state-checkbox" title="attr-command-type-state-checkbox">Checkbox</a> state</dt>
@@ -34120,7 +34117,7 @@
<dd><p>If the element has a <code title="attr-command-checked"><a href="#attr-command-checked">checked</a></code> attribute, the UA must
remove that attribute. Otherwise, the UA must add a <code title="attr-command-checked"><a href="#attr-command-checked">checked</a></code> attribute, with the
literal value <code title="">checked</code>. The UA must then
- <a href="#fire-a-click-event">fire a <code title="">click</code> event</a> at the
+ <a href="#fire-a-click-event">fire a <code title="event-click">click</code> event</a> at the
element.</dd>
@@ -34132,19 +34129,17 @@
<code><a href="#the-command">command</a></code> element, if that element has a <code title="attr-command-radiogroup"><a href="#attr-command-radiogroup">radiogroup</a></code> attribute whose
value exactly matches the current element's (treating missing <code title="attr-command-radiogroup"><a href="#attr-command-radiogroup">radiogroup</a></code> attributes as if
they were the empty string), and has a <code title="attr-command-checked"><a href="#attr-command-checked">checked</a></code> attribute, must remove
- that attribute and <a href="#fire-a-click-event">fire a <code title="">click</code>
- event</a> at the element.</p>
+ that attribute.</p>
<p>Then, the element's <code title="attr-command-checked"><a href="#attr-command-checked">checked</a></code> attribute attribute
must be set to the literal value <code title="">checked</code> and
- a <span title="file a click event"><code title="">click</code>
- event must be fired</span> at the element.</dd>
+ the user agent must <a href="#fire-a-click-event">fire a <code title="event-click">click</code>
+ event</a> at the element.</dd>
<dt>Otherwise</dt>
- <dd><p>The UA must <a href="#fire-a-click-event">fire a <code title="">click</code>
- event</a> at the element.</dd>
+ <dd><p>The element has no <a href="#activation-behavior">activation behavior</a>.</dd>
</dl><p class="note">Firing a synthetic <code title="event-click">click</code> event at the element does not cause
any of the actions described above to happen.</p>
@@ -34892,7 +34887,7 @@
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="">click</code> event</a> at the element.</p>
+ 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>
<h5 id="using-the-button-element-to-define-a-command"><span class="secno">4.11.6.2 </span><dfn title="button-command">Using the <code>button</code> element to define a command</dfn></h5>
@@ -34966,7 +34961,7 @@
attribute, and false otherwise.</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="">click</code> event</a> at the element.</p> <!-- XXX this
+ 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> <!-- XXX this
is probably wrong for radio and checkbox types, depending on how we
define <input>. -->
@@ -35071,10 +35066,13 @@
otherwise.</p>
<p>The <a href="#command-facet-action" title="command-facet-Action">Action</a> of the
- command is to invoke the behavior described in the definition of
- the <code title="dom-command-click"><a href="#dom-command-click">click()</a></code> method of the
- <code><a href="#htmlcommandelement">HTMLCommandElement</a></code> interface.</p> <!-- XXX update to
- point to dom-click when we remove dom-command-click -->
+ 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-bb-element-to-define-a-command"><span class="secno">4.11.6.6 </span><dfn title="bb-command">Using the <code>bb</code> element to define a command</dfn></h5>
Received on Wednesday, 17 June 2009 05:35:05 UTC