- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 14 Oct 2010 09:07:18 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv25106
Modified Files:
Overview.html
Log Message:
Drop DOMActivate (whatwg r5628)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4503
retrieving revision 1.4504
diff -u -d -r1.4503 -r1.4504
--- Overview.html 14 Oct 2010 08:53:55 -0000 1.4503
+++ Overview.html 14 Oct 2010 09:07:14 -0000 1.4504
@@ -2793,7 +2793,6 @@
<li><dfn id="uievent"><code>UIEvent</code></dfn> interface</li>
<li><dfn id="event-click" title="event-click"><code>click</code></dfn> event</li>
- <li><dfn id="event-domactivate" title="event-DOMActivate"><code>DOMActivate</code></dfn> event</li>
<li><dfn id="dom-event-target" title="dom-Event-target"><code>target</code></dfn> attribute</li>
@@ -9053,7 +9052,7 @@
behavior</a>, which means that the user can activate them. This
triggers a sequence of events dependent on the activation mechanism,
and normally culminating in a <code title="event-click"><a href="#event-click">click</a></code>
- event followed by a <code title="event-DOMActivate"><a href="#event-domactivate">DOMActivate</a></code> event<span class="impl">, as described below</span>.<div class="impl">
+ event<span class="impl">, as described below</span>.<div class="impl">
<p>The user agent should allow the user to manually trigger elements
that have an <a href="#activation-behavior">activation behavior</a>, for instance using
@@ -9119,22 +9118,15 @@
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> named <code title="event-DOMActivate"><a href="#event-domactivate">DOMActivate</a></code> that is cancelable at
- that element. The default action of this event must be to <a href="#run-final-activation-steps">run
- final activation steps</a> on that element. If the event is
- 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-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>
- <p>When a user agent is to <dfn id="run-final-activation-steps">run final activation steps</dfn> on
- an element, it must run the <dfn id="activation-behavior">activation behavior</dfn> defined
- for that element. Activation behaviors can refer to the <code title="event-click"><a href="#event-click">click</a></code> and <code title="event-DOMActivate"><a href="#event-domactivate">DOMActivate</a></code> events that were fired
- by the steps above leading up to this point.</p>
+ <p>When a user agent is to <dfn id="run-post-click-activation-steps">run post-click activation
+ steps</dfn> on an element, it must run the <dfn id="activation-behavior">activation
+ behavior</dfn> defined for that element. Activation behaviors can
+ refer to the <code title="event-click"><a href="#event-click">click</a></code> event that was
+ fired by the steps above leading up to this point.</p>
</div><h5 id="transparent-content-models"><span class="secno">3.2.5.2 </span>Transparent content models</h5><p>Some elements are described as <dfn id="transparent">transparent</dfn>; they have
"transparent" in the description of their content model.<p>When a content model includes a part that is "transparent", those
@@ -15744,7 +15736,7 @@
that create <a href="#hyperlink" title="hyperlink">hyperlinks</a> is to run the
following steps:</p>
- <ol><li><p>If the <code title="event-DOMActivate"><a href="#event-domactivate">DOMActivate</a></code>
+ <ol><li><p>If the <code title="event-click"><a href="#event-click">click</a></code>
event in question is not <a href="#concept-events-trusted" title="concept-events-trusted">trusted</a> (i.e. a <code title="dom-click"><a href="#dom-click">click()</a></code> method call was the reason for the
event being dispatched), and the <code><a href="#the-a-element">a</a></code> element's <code title="attr-hyperlink-target"><a href="#attr-hyperlink-target">target</a></code> attribute is such that
applying <a href="#the-rules-for-choosing-a-browsing-context-given-a-browsing-context-name">the rules for choosing a browsing context given a
@@ -15757,15 +15749,15 @@
event is an <code><a href="#the-img-element">img</a></code> element with an <code title="attr-img-ismap"><a href="#attr-img-ismap">ismap</a></code> attribute specified, then
server-side image map processing must be performed, as follows:</p>
- <ol><!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20html%3E%0A...%3Ca%20href%3D%22%23%22%3E%3Cimg%20ismap%20usemap%3D%22%23a%22%20src%3D/resources/images/smallcats%3E%3C/a%3E%0A%3Cmap%20name%3Da%3E%3Carea%20shape%3Drect%20coords%3D0%2C0%2C50%2C50%20href%3Db%3E%3C/map%3E --><li>If the <code title="event-DOMActivate"><a href="#event-domactivate">DOMActivate</a></code>
- event was dispatched as the result of a real
- pointing-device-triggered <code title="event-click"><a href="#event-click">click</a></code>
- event on the <code><a href="#the-img-element">img</a></code> element, then let <var title="">x</var> be the distance in CSS pixels from the left edge
- of the image's left border, if it has one, or the left edge of
- the image otherwise, to the location of the click, and let <var title="">y</var> be the distance in CSS pixels from the top edge
- of the image's top border, if it has one, or the top edge of the
- image otherwise, to the location of the click. Otherwise, let
- <var title="">x</var> and <var title="">y</var> be zero.</li>
+ <ol><!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20html%3E%0A...%3Ca%20href%3D%22%23%22%3E%3Cimg%20ismap%20usemap%3D%22%23a%22%20src%3D/resources/images/smallcats%3E%3C/a%3E%0A%3Cmap%20name%3Da%3E%3Carea%20shape%3Drect%20coords%3D0%2C0%2C50%2C50%20href%3Db%3E%3C/map%3E --><li>If the <code title="event-click"><a href="#event-click">click</a></code> event was a
+ real pointing-device-triggered <code title="event-click"><a href="#event-click">click</a></code> event on the <code><a href="#the-img-element">img</a></code>
+ element, then let <var title="">x</var> be the distance in CSS
+ pixels from the left edge of the image's left border, if it has
+ one, or the left edge of the image otherwise, to the location of
+ the click, and let <var title="">y</var> be the distance in CSS
+ pixels from the top edge of the image's top border, if it has
+ one, or the top edge of the image otherwise, to the location of
+ the click. Otherwise, let <var title="">x</var> and <var title="">y</var> be zero.</li>
<li>Let the <dfn id="hyperlink-suffix"><var>hyperlink suffix</var></dfn> be a U+003F
QUESTION MARK character, the value of <var title="">x</var>
@@ -24196,14 +24188,18 @@
<p>The <a href="#activation-behavior">activation behavior</a> of <code><a href="#the-area-element">area</a></code>
elements is to run the following steps:</p>
- <ol><li><p>If the <code title="event-DOMActivate"><a href="#event-domactivate">DOMActivate</a></code>
- event in question is not <a href="#concept-events-trusted" title="concept-events-trusted">trusted</a> (i.e. a <code title="dom-click"><a href="#dom-click">click()</a></code> method call was the reason for the
- event being dispatched), and the <code><a href="#the-area-element">area</a></code> element's <code title="attr-hyperlink-target"><a href="#attr-hyperlink-target">target</a></code> attribute is such that
- applying <a href="#the-rules-for-choosing-a-browsing-context-given-a-browsing-context-name">the rules for choosing a browsing context given a
- browsing context name</a>, using the value of the <code title="attr-hyperlink-target"><a href="#attr-hyperlink-target">target</a></code> attribute as the
- browsing context name, would result in there not being a chosen
- browsing context, then raise an <code><a href="#invalid_access_err">INVALID_ACCESS_ERR</a></code>
- exception and abort these steps.</li>
+ <ol><li><p>If the <code title="event-click"><a href="#event-click">click</a></code> event in
+ question is not <a href="#concept-events-trusted" title="concept-events-trusted">trusted</a>
+ (i.e. a <code title="dom-click"><a href="#dom-click">click()</a></code> method call was the
+ reason for the event being dispatched), and the <code><a href="#the-area-element">area</a></code>
+ element's <code title="attr-hyperlink-target"><a href="#attr-hyperlink-target">target</a></code>
+ attribute is such that applying <a href="#the-rules-for-choosing-a-browsing-context-given-a-browsing-context-name">the rules for choosing a
+ browsing context given a browsing context name</a>, using the
+ value of the <code title="attr-hyperlink-target"><a href="#attr-hyperlink-target">target</a></code>
+ attribute as the browsing context name, would result in there not
+ being a chosen browsing context, then raise an
+ <code><a href="#invalid_access_err">INVALID_ACCESS_ERR</a></code> exception and abort these
+ steps.</li>
<li>Otherwise, the user agent must <a href="#following-hyperlinks" title="following
hyperlinks">follow the hyperlink</a> created by the
@@ -68243,11 +68239,7 @@
<thead><tr><th> Event
<th> Interface
<th> Description
- <tbody><tr><td> <code title="event-DOMActivate"><a href="#event-domactivate">DOMActivate</a></code>
- <td> <code><a href="#event">Event</a></code>
- <td> Fired at an element before its <a href="#activation-behavior">activation behavior</a> is run
-
- <tr><td> <code title="event-DOMContentLoaded">DOMContentLoaded</code>
+ <tbody><tr><td> <code title="event-DOMContentLoaded">DOMContentLoaded</code>
<td> <code><a href="#event">Event</a></code>
<td> Fired at the <code><a href="#document">Document</a></code> once it and its scripts have loaded, without waiting for other subresources
@@ -68275,6 +68267,10 @@
<td> <code><a href="#event">Event</a></code>
<td> Fired at controls when the user commits a value change
+ <tr><td> <code title="event-click"><a href="#event-click">click</a></code>
+ <td> <code><a href="#event">Event</a></code>
+ <td> Fired at an element before its <a href="#activation-behavior">activation behavior</a> is run
+
<tr><td> <code title="event-contextmenu">contextmenu</code>
<td> <code><a href="#event">Event</a></code>
<td> Fired at elements when the user requests their context menu
Received on Thursday, 14 October 2010 09:07:21 UTC