[html5] r5628 - [giow] (2) Drop DOMActivate Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id [...]
whatwg at whatwg.org
whatwg at whatwg.org
Thu Oct 14 02:07:09 PDT 2010
Author: ianh
Date: 2010-10-14 02:07:08 -0700 (Thu, 14 Oct 2010)
New Revision: 5628
Modified:
complete.html
index
source
Log:
[giow] (2) Drop DOMActivate
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=10899
Modified: complete.html
===================================================================
--- complete.html 2010-10-14 08:53:47 UTC (rev 5627)
+++ complete.html 2010-10-14 09:07:08 UTC (rev 5628)
@@ -3238,7 +3238,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>
@@ -10486,7 +10485,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>.</p>
+ event<span class=impl>, as described below</span>.</p>
<div class=impl>
@@ -10554,22 +10553,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>
@@ -18097,7 +18089,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
@@ -18110,15 +18102,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>
@@ -33856,14 +33848,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
Modified: index
===================================================================
--- index 2010-10-14 08:53:47 UTC (rev 5627)
+++ index 2010-10-14 09:07:08 UTC (rev 5628)
@@ -3215,7 +3215,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>
@@ -10463,7 +10462,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>.</p>
+ event<span class=impl>, as described below</span>.</p>
<div class=impl>
@@ -10531,22 +10530,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>
@@ -18074,7 +18066,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
@@ -18087,15 +18079,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>
@@ -33836,14 +33828,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
@@ -88500,12 +88496,8 @@
<thead><tr><th> Event
<th> Interface
<th> Description
- <tbody><tr><td> <code title=event-DOMActivate><a href=#event-domactivate>DOMActivate</a></code>
+ <tbody><tr><td> <code title=event-DOMContentLoaded>DOMContentLoaded</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>
- <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
<tr><td> <code title=event-abort>abort</code>
@@ -88532,6 +88524,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
Modified: source
===================================================================
--- source 2010-10-14 08:53:47 UTC (rev 5627)
+++ source 2010-10-14 09:07:08 UTC (rev 5628)
@@ -2190,7 +2190,6 @@
<li><dfn><code>UIEvent</code></dfn> interface</li>
<li><dfn title="event-click"><code>click</code></dfn> event</li>
- <li><dfn title="event-DOMActivate"><code>DOMActivate</code></dfn> event</li>
<li><dfn title="dom-Event-target"><code>target</code></dfn> attribute</li>
@@ -10715,9 +10714,7 @@
behavior</span>, 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">click</code>
- event followed by a <code
- title="event-DOMActivate">DOMActivate</code> event<span
- class="impl">, as described below</span>.</p>
+ event<span class="impl">, as described below</span>.</p>
<div class="impl">
@@ -10796,25 +10793,15 @@
on an element, it must run the <dfn>pre-click activation steps</dfn>
defined for that element, if any.</p>
- <p>When a user agent is to <dfn>run post-click activation
- steps</dfn> on an element, the user agent must <span>fire a simple
- event</span> named <code
- title="event-DOMActivate">DOMActivate</code> that is cancelable at
- that element. The default action of this event must be to <span>run
- final activation steps</span> on that element. If the event is
- canceled, the user agent must <span>run canceled activation
- steps</span> on the element instead.</p>
-
<p>When a user agent is to <dfn>run canceled activation steps</dfn>
on an element, it must run the <dfn>canceled activation steps</dfn>
defined for that element, if any.</p>
- <p>When a user agent is to <dfn>run final activation steps</dfn> on
- an element, it must run the <dfn>activation behavior</dfn> defined
- for that element. Activation behaviors can refer to the <code
- title="event-click">click</code> and <code
- title="event-DOMActivate">DOMActivate</code> events that were fired
- by the steps above leading up to this point.</p>
+ <p>When a user agent is to <dfn>run post-click activation
+ steps</dfn> on an element, it must run the <dfn>activation
+ behavior</dfn> defined for that element. Activation behaviors can
+ refer to the <code title="event-click">click</code> event that was
+ fired by the steps above leading up to this point.</p>
</div>
@@ -19256,7 +19243,7 @@
<ol>
- <li><p>If the <code title="event-DOMActivate">DOMActivate</code>
+ <li><p>If the <code title="event-click">click</code>
event in question is not <span
title="concept-events-trusted">trusted</span> (i.e. a <code
title="dom-click">click()</code> method call was the reason for the
@@ -19278,17 +19265,17 @@
<!-- 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">DOMActivate</code>
- event was dispatched as the result of a real
- pointing-device-triggered <code title="event-click">click</code>
- event on the <code>img</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>If the <code title="event-click">click</code> event was a
+ real pointing-device-triggered <code
+ title="event-click">click</code> event on the <code>img</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><var>hyperlink suffix</var></dfn> be a U+003F
QUESTION MARK character, the value of <var title="">x</var>
@@ -37447,18 +37434,18 @@
<ol>
- <li><p>If the <code title="event-DOMActivate">DOMActivate</code>
- event in question is not <span
- title="concept-events-trusted">trusted</span> (i.e. a <code
- title="dom-click">click()</code> method call was the reason for the
- event being dispatched), and the <code>area</code> element's <code
- title="attr-hyperlink-target">target</code> attribute is such that
- applying <span>the rules for choosing a browsing context given a
- browsing context name</span>, using the value of the <code
- title="attr-hyperlink-target">target</code> attribute as the
- browsing context name, would result in there not being a chosen
- browsing context, then raise an <code>INVALID_ACCESS_ERR</code>
- exception and abort these steps.</p></li>
+ <li><p>If the <code title="event-click">click</code> event in
+ question is not <span title="concept-events-trusted">trusted</span>
+ (i.e. a <code title="dom-click">click()</code> method call was the
+ reason for the event being dispatched), and the <code>area</code>
+ element's <code title="attr-hyperlink-target">target</code>
+ attribute is such that applying <span>the rules for choosing a
+ browsing context given a browsing context name</span>, using the
+ value of the <code title="attr-hyperlink-target">target</code>
+ attribute as the browsing context name, would result in there not
+ being a chosen browsing context, then raise an
+ <code>INVALID_ACCESS_ERR</code> exception and abort these
+ steps.</p></li>
<li>Otherwise, the user agent must <span title="following
hyperlinks">follow the hyperlink</span> created by the
@@ -106082,11 +106069,6 @@
<tbody>
<tr>
- <td> <code title="event-DOMActivate">DOMActivate</code>
- <td> <code>Event</code>
- <td> Fired at an element before its <span>activation behavior</span> is run
-
- <tr>
<td> <code title="event-DOMContentLoaded">DOMContentLoaded</code>
<td> <code>Event</code>
<td> Fired at the <code>Document</code> once it and its scripts have loaded, without waiting for other subresources
@@ -106122,6 +106104,11 @@
<td> Fired at controls when the user commits a value change
<tr>
+ <td> <code title="event-click">click</code>
+ <td> <code>Event</code>
+ <td> Fired at an element before its <span>activation behavior</span> is run
+
+ <tr>
<td> <code title="event-contextmenu">contextmenu</code>
<td> <code>Event</code>
<td> Fired at elements when the user requests their context menu
More information about the Commit-Watchers
mailing list