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
I'm investigating a flaky test for VS Code (microsoft/vscode#90470). Through logging, I have noticed that the root cause of the flaky test is that blur and focus events are not delivered to DOM nodes in Chromium.
Basically, in that test something like the following happens:
textArea1.focus()
document.activeElement === textArea1 (true)
textArea2.focus()
document.activeElement === textArea2 (true)
But no blur event is delivered to textArea1, document.activeElement changes without notifying the old focused element that it got blurred. I can try creating a simple repro if you want, just let me know.
What is interesting is that if I click in the page and interact with it, it's like all those events were queued up and then they all fire.
The text was updated successfully, but these errors were encountered:
Context:
I'm investigating a flaky test for VS Code (microsoft/vscode#90470). Through logging, I have noticed that the root cause of the flaky test is that
blur
andfocus
events are not delivered to DOM nodes in Chromium.Basically, in that test something like the following happens:
textArea1.focus()
document.activeElement === textArea1
(true
)textArea2.focus()
document.activeElement === textArea2
(true
)But no
blur
event is delivered totextArea1
,document.activeElement
changes without notifying the old focused element that it got blurred. I can try creating a simple repro if you want, just let me know.What is interesting is that if I click in the page and interact with it, it's like all those events were queued up and then they all fire.
The text was updated successfully, but these errors were encountered: