W3C home > Mailing lists > Public > public-html-diffs@w3.org > April 2010

hixie: s/span/code/ for some event identifiers (whatwg r4955)

From: poot <cvsmail@w3.org>
Date: Fri, 2 Apr 2010 15:31:18 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20100402063118.67B9A2BC52@toro.w3.mag.keio.ac.jp>
hixie: s/span/code/ for some event identifiers (whatwg r4955)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.3976&r2=1.3977&f=h
http://html5.org/tools/web-apps-tracker?from=4954&to=4955

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3976
retrieving revision 1.3977
diff -u -d -r1.3976 -r1.3977
--- Overview.html	2 Apr 2010 06:26:50 -0000	1.3976
+++ Overview.html	2 Apr 2010 06:31:01 -0000	1.3977
@@ -8383,7 +8383,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>
@@ -8419,7 +8419,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
@@ -31206,7 +31206,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
@@ -31243,7 +31243,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
@@ -45912,7 +45912,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>
Received on Friday, 2 April 2010 06:31:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 06:14:18 GMT