[html5] r4955 - [e] (0) s/span/code/ for some event identifiers Fixing http://www.w3.org/Bugs/Pu [...]
whatwg at whatwg.org
whatwg at whatwg.org
Thu Apr 1 23:30:57 PDT 2010
Author: ianh
Date: 2010-04-01 23:30:56 -0700 (Thu, 01 Apr 2010)
New Revision: 4955
Modified:
complete.html
index
source
Log:
[e] (0) s/span/code/ for some event identifiers
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=9348
Modified: complete.html
===================================================================
--- complete.html 2010-04-02 06:26:46 UTC (rev 4954)
+++ complete.html 2010-04-02 06:30:56 UTC (rev 4955)
@@ -9819,7 +9819,7 @@
<p>When a user agent is to <dfn id=run-synthetic-click-activation-steps>run synthetic click activation
steps</dfn> on an element, the user agent must <a href=#run-pre-click-activation-steps>run pre-click
activation steps</a> on the element, then <a href=#fire-a-click-event>fire a <code title=event-click>click</code> event</a> at the element. The
- default action of this <a href=#event-click title=event-click>click</a> event
+ default action of this <code title=event-click><a href=#event-click>click</a></code> event
must be to <a href=#run-post-click-activation-steps>run post-click activation steps</a> on the
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>
@@ -9855,7 +9855,7 @@
event.</p> <!-- interaction event spec point -->
<p>If there is an element <var title="">e</var>, then the default
- action of the <a href=#event-click title=event-click>click</a> event must be
+ action of the <code title=event-click><a href=#event-click>click</a></code> event must be
to <a href=#run-post-click-activation-steps>run post-click activation steps</a> on element <var title="">e</var>.</p>
<p>If there is an element <var title="">e</var> but the event is
@@ -38605,7 +38605,7 @@
a <a href=#using-the-option-element-to-define-a-command title=option-command>menu command</a>, or through any
other mechanism), and before the relevant user interaction event
<!-- interaction event spec point --> is queued (e.g. before the
- <a href=#event-click title=event-click>click</a> event), the user agent must
+ <code title=event-click><a href=#event-click>click</a></code> event), the user agent must
set the <a href=#concept-option-selectedness title=concept-option-selectedness>selectedness</a> of the
picked <code><a href=#the-option-element>option</a></code> element to true and then <a href=#queue-a-task>queue a
task</a> to <a href=#fire-a-simple-event>fire a simple event</a> that bubbles named
@@ -38642,7 +38642,7 @@
mechanism). Upon the <a href=#concept-option-selectedness title=concept-option-selectedness>selectedness</a> of one or
more <code><a href=#the-option-element>option</a></code> elements being changed by the user, and
before the relevant user interaction event <!-- interaction event
- spec point --> is queued (e.g. before a related <a href=#event-click title=event-click>click</a> event), the user agent must
+ spec point --> is queued (e.g. before a related <code title=event-click><a href=#event-click>click</a></code> event), the user agent must
<a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a> that
bubbles named <code title=event-change>change</code> at the
<code><a href=#the-select-element>select</a></code> element, using the <a href=#user-interaction-task-source>user interaction task
@@ -59354,7 +59354,7 @@
<p>This <a href=#task-source>task source</a> is used for features that react
to user interaction, for example keyboard or mouse input.</p>
- <p>Asynchronous events sent in response to user input (e.g. <a href=#event-click title=event-click>click</a> events) must be dispatched using
+ <p>Asynchronous events sent in response to user input (e.g. <code title=event-click><a href=#event-click>click</a></code> events) must be dispatched using
<a href=#concept-task title=concept-task>tasks</a> <a href=#queue-a-task title="queue a
task">queued</a> with the <a href=#user-interaction-task-source>user interaction task
source</a>. <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p>
Modified: index
===================================================================
--- index 2010-04-02 06:26:46 UTC (rev 4954)
+++ index 2010-04-02 06:30:56 UTC (rev 4955)
@@ -9717,7 +9717,7 @@
<p>When a user agent is to <dfn id=run-synthetic-click-activation-steps>run synthetic click activation
steps</dfn> on an element, the user agent must <a href=#run-pre-click-activation-steps>run pre-click
activation steps</a> on the element, then <a href=#fire-a-click-event>fire a <code title=event-click>click</code> event</a> at the element. The
- default action of this <a href=#event-click title=event-click>click</a> event
+ default action of this <code title=event-click><a href=#event-click>click</a></code> event
must be to <a href=#run-post-click-activation-steps>run post-click activation steps</a> on the
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>
@@ -9753,7 +9753,7 @@
event.</p> <!-- interaction event spec point -->
<p>If there is an element <var title="">e</var>, then the default
- action of the <a href=#event-click title=event-click>click</a> event must be
+ action of the <code title=event-click><a href=#event-click>click</a></code> event must be
to <a href=#run-post-click-activation-steps>run post-click activation steps</a> on element <var title="">e</var>.</p>
<p>If there is an element <var title="">e</var> but the event is
@@ -38506,7 +38506,7 @@
a <a href=#using-the-option-element-to-define-a-command title=option-command>menu command</a>, or through any
other mechanism), and before the relevant user interaction event
<!-- interaction event spec point --> is queued (e.g. before the
- <a href=#event-click title=event-click>click</a> event), the user agent must
+ <code title=event-click><a href=#event-click>click</a></code> event), the user agent must
set the <a href=#concept-option-selectedness title=concept-option-selectedness>selectedness</a> of the
picked <code><a href=#the-option-element>option</a></code> element to true and then <a href=#queue-a-task>queue a
task</a> to <a href=#fire-a-simple-event>fire a simple event</a> that bubbles named
@@ -38543,7 +38543,7 @@
mechanism). Upon the <a href=#concept-option-selectedness title=concept-option-selectedness>selectedness</a> of one or
more <code><a href=#the-option-element>option</a></code> elements being changed by the user, and
before the relevant user interaction event <!-- interaction event
- spec point --> is queued (e.g. before a related <a href=#event-click title=event-click>click</a> event), the user agent must
+ spec point --> is queued (e.g. before a related <code title=event-click><a href=#event-click>click</a></code> event), the user agent must
<a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a> that
bubbles named <code title=event-change>change</code> at the
<code><a href=#the-select-element>select</a></code> element, using the <a href=#user-interaction-task-source>user interaction task
@@ -59275,7 +59275,7 @@
<p>This <a href=#task-source>task source</a> is used for features that react
to user interaction, for example keyboard or mouse input.</p>
- <p>Asynchronous events sent in response to user input (e.g. <a href=#event-click title=event-click>click</a> events) must be dispatched using
+ <p>Asynchronous events sent in response to user input (e.g. <code title=event-click><a href=#event-click>click</a></code> events) must be dispatched using
<a href=#concept-task title=concept-task>tasks</a> <a href=#queue-a-task title="queue a
task">queued</a> with the <a href=#user-interaction-task-source>user interaction task
source</a>. <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p>
Modified: source
===================================================================
--- source 2010-04-02 06:26:46 UTC (rev 4954)
+++ source 2010-04-02 06:30:56 UTC (rev 4955)
@@ -9913,7 +9913,7 @@
steps</dfn> on an element, the user agent must <span>run pre-click
activation steps</span> on the element, then <span>fire a <code
title="event-click">click</code> event</span> at the element. The
- default action of this <span title="event-click">click</span> event
+ default action of this <code title="event-click">click</code> event
must be to <span>run post-click activation steps</span> on the
element. If the event is canceled, the user agent must <span>run
canceled activation steps</span> on the element instead.</p>
@@ -9955,7 +9955,7 @@
event.</p> <!-- interaction event spec point -->
<p>If there is an element <var title="">e</var>, then the default
- action of the <span title="event-click">click</span> event must be
+ action of the <code title="event-click">click</code> event must be
to <span>run post-click activation steps</span> on element <var
title="">e</var>.</p>
@@ -42853,7 +42853,7 @@
a <span title="option-command">menu command</span>, or through any
other mechanism), and before the relevant user interaction event
<!-- interaction event spec point --> is queued (e.g. before the
- <span title="event-click">click</span> event), the user agent must
+ <code title="event-click">click</code> event), the user agent must
set the <span
title="concept-option-selectedness">selectedness</span> of the
picked <code>option</code> element to true and then <span>queue a
@@ -42907,8 +42907,8 @@
title="concept-option-selectedness">selectedness</span> of one or
more <code>option</code> elements being changed by the user, and
before the relevant user interaction event <!-- interaction event
- spec point --> is queued (e.g. before a related <span
- title="event-click">click</span> event), the user agent must
+ spec point --> is queued (e.g. before a related <code
+ title="event-click">click</code> event), the user agent must
<span>queue a task</span> to <span>fire a simple event</span> that
bubbles named <code title="event-change">change</code> at the
<code>select</code> element, using the <span>user interaction task
@@ -66982,8 +66982,8 @@
<p>This <span>task source</span> is used for features that react
to user interaction, for example keyboard or mouse input.</p>
- <p>Asynchronous events sent in response to user input (e.g. <span
- title="event-click">click</span> events) must be dispatched using
+ <p>Asynchronous events sent in response to user input (e.g. <code
+ title="event-click">click</code> events) must be dispatched using
<span title="concept-task">tasks</span> <span title="queue a
task">queued</span> with the <span>user interaction task
source</span>. <a href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
More information about the Commit-Watchers
mailing list