You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
From WHATWG: a11y concerns around removing the blur event on element removal #2920
@noamr is trying to make Blink stop synchronously firing the blur event when an element is removed from the page.
In his Intent to Deprecate thread, someone was concerned that this would negatively impact focus tracking code that depends on this event. @noamr has been researching this potential impact, but he would like to hear a11y folks' opinions. Interested in both estimates of how widespread this dependency might be, and if they foresee any problems with his proposed replacement focusreset
The spec doesn't fire blur/change/focusout events when a focus element is removed.
Gecko/WebKit already don't fire those events, while Blink still does.
There are some tools that rely on blur events, but seem like they have somewhat hacky workarounds for the missing events in Gecko/WebKit (such as mutation observers or setInterval)
Our plan is to align with Gecko/WebKit, and also introduce a document async focusreset event when the focus has been reset due to element removal or some such
This whole thing does not affect blur/change events in other situations.
What we would like:
To hear specific concerns from the a11y community about this, if applicable
Alternatively, get the a11y community's blessing for this change.
Activity
noamr commentedon Sep 30, 2026
To clarify:
setInterval)focusresetevent when the focus has been reset due to element removal or some suchWhat we would like:
spectranaut commentedon Oct 19, 2026
This topic will be discussed at a joint meeting between WHATWG and ARIA on Thursday at TPAC, 13:45-14:30 local time: https://github.com/w3c/aria/wiki/TPAC-2026#thursday-oct-29-2026