Skip to content

Commit

Permalink
[e] (0) fix confusion in activation behavior text (credit: lh)
Browse files Browse the repository at this point in the history
git-svn-id: http://svn.whatwg.org/webapps@2453 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Nov 26, 2008
1 parent 8906d36 commit 54708c0
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 10 deletions.
10 changes: 5 additions & 5 deletions index
Expand Up @@ -6889,11 +6889,11 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
<p>Certain elements in HTML have an <a href=#activation-behavior>activation
behavior</a>, which means the user agent should allow the user to
manually trigger them in some way, for instance using keyboard or
voice input (though not mouse clicks, which are handled above). When
the user triggers an element with a defined <a href=#activation-behavior>activation
behavior</a>, the default action of the interaction event<!-- XXX
--> must be to <a href=#run-synthetic-click-activation-steps>run synthetic click activation steps</a> on
the element.</p>
voice input, or through mouse clicks. When the user triggers an
element with a defined <a href=#activation-behavior>activation behavior</a> in a manner
other than clicking it, the default action of the interaction
event<!-- XXX --> must be to <a href=#run-synthetic-click-activation-steps>run synthetic click activation
steps</a> on the element.</p>

<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
Expand Down
10 changes: 5 additions & 5 deletions source
Expand Up @@ -7005,11 +7005,11 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
<p>Certain elements in HTML have an <span>activation
behavior</span>, which means the user agent should allow the user to
manually trigger them in some way, for instance using keyboard or
voice input (though not mouse clicks, which are handled above). When
the user triggers an element with a defined <span>activation
behavior</span>, the default action of the interaction event<!-- XXX
--> must be to <span>run synthetic click activation steps</span> on
the element.</p>
voice input, or through mouse clicks. When the user triggers an
element with a defined <span>activation behavior</span> in a manner
other than clicking it, the default action of the interaction
event<!-- XXX --> must be to <span>run synthetic click activation
steps</span> on the element.</p>

<p>When a user agent is to <dfn>run synthetic click activation
steps</dfn> on an element, the user agent must <span>run pre-click
Expand Down

0 comments on commit 54708c0

Please sign in to comment.