From 457f1d52094a7e53579d3814aeb3e5b0ed8525d7 Mon Sep 17 00:00:00 2001
From: Ian Hickson The User agents should run the unfocusing steps for an
- element whenever the user moves the focus away from any
- focusable element. When the user moves the focus away from a focusable
+ element, the user agent should run the unfocusing steps
+ that element. When an element that is focused stops being a
+ focusable element, the user agent should run the
+ unfocusing steps that element. For example, this might happen because the
+ element is removed from its An element is focusable if the
+
+
+
a
elements that have an href
attributearea
elements that have an href
attributelink
elements that have an href
attributebb
elements whose type
attribute is in a state whose
+ relevance is truebutton
elements that are not disabledinput
elements whose type
attribute are not in the
+ Hidden state and that
+ are not disabledselect
elements that are not disabledtextarea
elements that are not disabledcommand
elements that do not have a disabled
attributetabIndex
DOM
attribute must reflect the value of the tabindex
content attribute. If the
attribute is not present, or parsing its value returns an error,
@@ -45518,9 +45556,17 @@ at the first element with the given ID must be treated as if it was cloned and r
- Document
, or has a hidden
attribute added. It would also
+ happen to an input
element when the element gets disabled.6.5.3 Document-level focus APIs
diff --git a/source b/source
index b8f33e6a847..525800da0bf 100644
--- a/source
+++ b/source
@@ -38255,7 +38255,8 @@ explain that only direct children of the command
elements that do not have a disabled
attributeAn element is specially focusable if the
tabindex
attribute's definition above
- defines the element to be focusable and the element is
- being rendered.
An element that is focusable but does not otherwise - have an activation behavior defined has an +
An element that is specially focusable but does not + otherwise have an activation behavior defined has an activation behavior that does nothing.
This means that an element that is only focusable @@ -48629,6 +48629,53 @@ at the first element with the given ID must be treated as if it was cloned and r to a non-mouse activation (e.g. hitting the "enter" key while the element is focused).
+An element is focusable if the user agent's default + behavior allows it to be focusable or if the element is + specially focusable, but only if the element is + being rendered.
+ +User agents should make the following elements + focusable, unless platform conventions dictate + otherwise:
+ +a
elements that have an href
attributearea
elements that have an href
attributelink
elements that have an href
attributebb
elements whose type
attribute is in a state whose
+ relevance is truebutton
elements that are not disabledinput
elements whose type
attribute are not in the
+ Hidden state and that
+ are not disabledselect
elements that are not disabledtextarea
elements that are not disabledcommand
elements that do not have a disabled
attributeThe tabIndex
DOM
attribute must reflect the value of the tabindex
content attribute. If the
@@ -48693,9 +48740,19 @@ at the first element with the given ID must be treated as if it was cloned and r
-
User agents should run the unfocusing steps for an - element whenever the user moves the focus away from any - focusable element.
+When the user moves the focus away from a focusable + element, the user agent should run the unfocusing steps + that element.
+ +When an element that is focused stops being a + focusable element, the user agent should run the + unfocusing steps that element.
+ +For example, this might happen because the
+ element is removed from its Document
, or has a hidden
attribute added. It would also
+ happen to an input
element when the element gets disabled.