Closed Bug 1649099 Opened 10 months ago Closed 8 months ago

Add WPTs for testing the effect on activeElement of the containing doc when calling .focus() and .blur() on an OOP iframe

Categories

(Core :: DOM: UI Events & Focus Handling, task, P2)

task

Tracking

()

RESOLVED FIXED
82 Branch
Fission Milestone M6c
Tracking Status
firefox82 --- fixed

People

(Reporter: hsivonen, Assigned: hsivonen)

References

(Blocks 1 open bug)

Details

(Whiteboard: ETA: 9/15, [wptsync upstream])

Attachments

(1 file)

No description provided.

As a surprise, the different-site case passes in Fission. I'll use Pernosco to figure out why.

(In reply to Henri Sivonen (:hsivonen) from comment #2)

As a surprise, the different-site case passes in Fission. I'll use Pernosco to figure out why.

Things are OK after onload. Need to write more tests for the case before onload.

Severity: -- → S3
Priority: -- → P1

Here are the cases that differ between Chrome and Firefox:

/focus/activeelement-after-immediately-focusing-different-site-iframe-contentwindow.html

Chrome
"outerparser,activeElement:BODY,willfocusiframe,didfocusiframe,activeElement:IFRAME,willbluriframe,didbluriframe,activeElement:IFRAME,willspineventloop,"

Firefox without Fission
"outerparser,activeElement:BODY,willfocusiframe,didfocusiframe,activeElement:IFRAME,willbluriframe,didbluriframe,activeElement:IFRAME,willspineventloop,innerbodyfocus,"

Firefox with Fission
"outeronload,activeElement:BODY,willfocusiframe,didfocusiframe,activeElement:BODY,willbluriframe,didbluriframe,activeElement:BODY,willspineventloop,innerbodyfocus,"

/focus/activeelement-after-immediately-focusing-different-site-iframe.html

Chrome
"outerparser,activeElement:BODY,willfocusiframe,didfocusiframe,activeElement:IFRAME,willbluriframe,didbluriframe,activeElement:BODY,willspineventloop,"

Firefox without Fission
"outerparser,activeElement:BODY,willfocusiframe,didfocusiframe,activeElement:BODY,willbluriframe,didbluriframe,activeElement:BODY,willspineventloop,"

Firefox with Fission
"outerparser,activeElement:BODY,willfocusiframe,didfocusiframe,activeElement:BODY,willbluriframe,didbluriframe,activeElement:BODY,willspineventloop,"

/focus/activeelement-after-immediately-focusing-same-site-iframe-contentwindow.html

Chrome
"outerparse,activeElement:BODY,willfocusiframe,didfocusiframe,activeElement:IFRAME,willbluriframe,didbluriframe,activeElement:IFRAME,willspineventloop,"

Firefox without Fission
"outerparse,activeElement:BODY,willfocusiframe,didfocusiframe,activeElement:IFRAME,willbluriframe,didbluriframe,activeElement:IFRAME,willspineventloop,innerbodyfocus,"

Firefox with Fission
"outerparse,activeElement:BODY,willfocusiframe,didfocusiframe,activeElement:IFRAME,willbluriframe,didbluriframe,activeElement:IFRAME,willspineventloop,innerbodyfocus,"

/focus/activeelement-after-immediately-focusing-same-site-iframe.html

Chrome
"outerparse,activeElement:BODY,willfocusiframe,didfocusiframe,activeElement:IFRAME,willbluriframe,didbluriframe,activeElement:BODY,willspineventloop,"

Firefox without Fission
"outerparse,activeElement:BODY,willfocusiframe,didfocusiframe,activeElement:BODY,willbluriframe,didbluriframe,activeElement:BODY,willspineventloop,"

Firefox with Fission
"outerparse,activeElement:BODY,willfocusiframe,didfocusiframe,activeElement:BODY,willbluriframe,didbluriframe,activeElement:BODY,willspineventloop,"

(In reply to Henri Sivonen (:hsivonen) from comment #5)

Here are the cases that differ between Chrome and Firefox:

The primary observation is that Chrome's results don't differ between same-site and different-site. That seems like a good sign.

contentWindow

Different-site in Firefox via contentWindow differs between Fission and non-Fission. (Do sites actually care about contentWindow? We have a pre-existing unit test that does.)

The document inside the iframe fires a focus event in Firefox but not in Chrome. Blur isn't observable in either.

Element

Firefox fails to focus with or without Fission even though Chrome focuses.

annevk, any thoughts on the focus event observability difference in the contentWindow case?

Flags: needinfo?(annevk)

Nothing concrete unfortunately. I think our focus should be on getting the browsers, tests, and the standard in alignment. We should not have behavior differences between Fission and non-Fission (same-origin vs cross-origin or same-site vs cross-site differences are okay though).

Flags: needinfo?(annevk)

We should do this as soon as possible in M6.

Fission Milestone: --- → M6c
Priority: P1 → P2
Pushed by hsivonen@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5ca78eb969aa
Add WPTs for testing the effect on activeElement of the containing doc when calling .focus() and .blur() on an OOP iframe. r=jgraham
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/25456 for changes under testing/web-platform/tests
Whiteboard: ETA: 9/15
Pushed by hsivonen@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/05cc29ef24ba
Add WPTs for testing the effect on activeElement of the containing doc when calling .focus() and .blur() on an OOP iframe. r=jgraham
Whiteboard: ETA: 9/15 → ETA: 9/15, [wptsync upstream]
Status: ASSIGNED → RESOLVED
Closed: 8 months ago
Resolution: --- → FIXED
Target Milestone: --- → 82 Branch
Upstream PR merged by moz-wptsync-bot
You need to log in before you can comment on or make changes to this bug.