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
My exprience shows, that WebKit does not set document.activeElement when clicking by mouse. Firefox and Chrome set document.activeElement when clicking by mouse. All browsers set document.activeElement, when navigating with keyboard.
I haven't been able to reproduce the issue on any version of Safari, and we don't currently track data for other (currently-)WebKit-based browsers. The bug's title says [GTK], so I'm assuming this was an issue that only affected GTK-based WebKit browsers.
https://caniuse.com/mdn-api_document_activeelement says
document.activeElement
is supported by WebKit/Safari.My exprience shows, that WebKit does not set
document.activeElement
when clicking by mouse. Firefox and Chrome setdocument.activeElement
when clicking by mouse. All browsers setdocument.activeElement
, when navigating with keyboard.https://bugs.webkit.org/show_bug.cgi?id=236217 contains details and sample snippet for reproduction.
The text was updated successfully, but these errors were encountered: