[giow] (2) Drop DOMActivate

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=10899 git-svn-id: http://svn.whatwg.org/webapps@5628 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Oct 14, 2010 · b61270b · b61270b
1 parent 8296a5a
commit b61270b
Show file tree

Hide file tree

Showing 3 changed files with 96 additions and 117 deletions.
diff --git a/complete.html b/complete.html
@@ -3238,7 +3238,6 @@ <h4 id=dependencies><span class=secno>2.2.1 </span>Dependencies</h4>
      <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>
 
@@ -10486,7 +10485,7 @@ <h6 id=interactive-content-0><span class=secno>3.2.5.1.7 </span>Interactive cont
   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>.</p>
+  event<span class=impl>, as described below</span>.</p>
 
   <div class=impl>
 
@@ -10554,22 +10553,15 @@ <h6 id=interactive-content-0><span class=secno>3.2.5.1.7 </span>Interactive cont
   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>
 
@@ -18097,7 +18089,7 @@ <h4 id=the-a-element><span class=secno>4.6.1 </span>The <dfn><code>a</code></dfn
   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
@@ -18110,15 +18102,15 @@ <h4 id=the-a-element><span class=secno>4.6.1 </span>The <dfn><code>a</code></dfn
    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>
@@ -33856,14 +33848,18 @@ <h4 id=the-area-element><span class=secno>4.8.13 </span>The <dfn><code>area</cod
   <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

diff --git a/index b/index
@@ -3215,7 +3215,6 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
      <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>
 
@@ -10463,7 +10462,7 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
   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>.</p>
+  event<span class=impl>, as described below</span>.</p>
 
   <div class=impl>
 
@@ -10531,22 +10530,15 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
   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>
 
@@ -18074,7 +18066,7 @@ included with Exhibit B.
   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
@@ -18087,15 +18079,15 @@ included with Exhibit B.
    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>
@@ -33836,14 +33828,18 @@ function AddCloud(data, x, y) { ... }</pre>
   <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
@@ -88500,11 +88496,7 @@ interface <a href=#htmldocument>HTMLDocument</a> {
    <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
 
@@ -88532,6 +88524,10 @@ interface <a href=#htmldocument>HTMLDocument</a> {
      <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