Test expects `document.activeElement` staying on the last focusable element (<a>) of the iframe after focus moves out of iframe by tab navigation. But with xorigin and fission enabled, the `document.activeElement` is reset to document after focus moves out of the iframe. In other browsers, `document.activeElement` is reset to document after focus moves out of iframe. So it seems like the test expectation is wrong, and we have a bug on non-fission iframe. The OOP iframe somehow behavior correct, at least compate with other browsers.
Bug 1661682 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Test expects `document.activeElement` staying on the last focusable element (<a>) of the iframe after focus moves out of iframe by tab navigation. But with xorigin and fission enabled, the `document.activeElement` is reset to document after focus moves out of the iframe. In other browsers, `document.activeElement` is reset to document after focus moves out of iframe. So it seems like the test expectation is wrong, and we have a bug on non-fission iframe. The OOP iframe somehow behavior correct, at least compare with other browsers.