Permalink
Browse files

Port whatwg/html#2003 but retain/rewrite note (#704)

LGTM thanks @patrickhlauke
  • Loading branch information...
patrickhlauke authored and stevefaulkner committed Nov 4, 2016
1 parent 1f582bb commit 6383af0e64d70d50dec5b185bbf962b2658ca482
Showing with 3 additions and 13 deletions.
  1. +3 −13 sections/editing.include
View
@@ -713,13 +713,6 @@
</ul>
<p class="note">
One valid reason to ignore the platform conventions and always allow an element
to be focused (by setting its <a>tabindex focus flag</a>) would be if the user's only
mechanism for activating an element is through a keyboard action that triggers the focused
element.
</p>
</dd>
<dt>If the value is a negative integer</dt>
@@ -789,13 +782,10 @@
</dl>
An element that has its <a>tabindex focus flag</a> set but does not otherwise have an
<a>activation behavior</a> defined has an <a>activation behavior</a> that does
nothing.
<p class="note">
This means that an element that is only focusable because of its <code>tabindex</code> attribute will fire a <code>click</code> event in response to a non-mouse activation (e.g., hitting the
"enter" key while the element is <a>focused</a>).
In current user agent implementations, an element that is only focusable because of its <code>tabindex</code>
attribute will generally <em>not</em> fire a <code>click</code> event in response to a non-mouse activation
(e.g., hitting the "enter" key while the element is <a>focused</a>).
</p>
An element with the <code>tabindex</code> attribute specified is

0 comments on commit 6383af0

Please sign in to comment.