/html/semantics/embedded-content/the-iframe-element/iframe_sandbox_popups_escaping-3.html would in certain cases CRASH, described and fixed at: #39745
Now it should only intermittently TIMEOUT(when no message event is fired), and the reason for that seems to be that the iframe and the pop-up share a webview(post navigation of the pop-up?), and then the pop-up sends a message to the iframe, and closes itself. The closure ends-up closing the webview at the constellation, and then if the message hasn't been received by the iframe, then receiving it will result in the iframe receiving none(and previously crashing) in response to GetBrowsingContextInfo. The weird part is that the webview that the constellation reports as closed is the one in which the iframe conceptually finds itself.
This is the underlying problem of symptoms like
/html/semantics/embedded-content/the-iframe-element/iframe_sandbox_popups_escaping-3.htmlwould in certain cases CRASH, described and fixed at: #39745Now it should only intermittently TIMEOUT(when no message event is fired),
and the reason for that seems to be that the iframe and the pop-up share a webview(post navigation of the pop-up?),and then the pop-up sends a message to the iframe, and closes itself. The closure ends-up closing the webview at the constellation, and then if the message hasn't been received by the iframe, then receiving it will result in the iframe receiving none(and previously crashing) in response toGetBrowsingContextInfo.The weird part is that the webview that the constellation reports as closed is the one in which the iframe conceptually finds itself.This is the underlying problem of symptoms like