1660752 - Make test_bug238987.html pass with cross-origin and Fission enabled

Status: RESOLVED FIXED

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

Description

[Edgar Chen [:edgar]]

Test got unexpected focus events before the first tab navigation. Look like there are timing changes in focus event.

Comment 1

[Edgar Chen [:edgar]]

Attachment: test.html

(In reply to Edgar Chen [:edgar] from comment #0)

Test got unexpected focus events before the first tab navigation. Look like there are timing changes in focus event.

Here is the test page that shows the differences:

Fission

With fission enabled, the focus event is dispatched asynchronously.

onload
before calling window.focus()
after calling window.focus()
window.onfocus: target: [object HTMLDocument], eventPhase: 1
window.onfocus: target: [object Window], eventPhase: 2
window.onfocus: target: [object Window], eventPhase: 2

non-Fission

The focus event used to be dispatched synchronously while calling window.focus() of the iframe.

onload
before calling window.focus()
window.onfocus: target: [object HTMLDocument], eventPhase: 1
window.onfocus: target: [object Window], eventPhase: 2
window.onfocus: target: [object Window], eventPhase: 2
after calling window.focus()

Henri, is this something expected? If so, I will modify the test to make it compatible with fission.

Comment 2

[Henri Sivonen (:hsivonen)]

.contentWindow.focus() on an OOP iframe is known broken in general: Bug 1613054.

As for sync vs. async, I'm not yet sure where that part will settle.

Comment 3

[Edgar Chen [:edgar]]

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

.contentWindow.focus() on an OOP iframe is known broken in general: Bug 1613054.

As for sync vs. async, I'm not yet sure where that part will settle.

Thanks!

Comment 4

[Chris Peterson [:cpeterson]]

Tracking for Fission Nightly M6c

Comment 5

[Jens Stutte [:jstutte]]

Hi Chris, does M6c here mean, it should no longer block bug 1653457 (marked M6b) ?

Comment 6

[Chris Peterson [:cpeterson]]

(In reply to Jens Stutte [:jstutte] (REO for FF 81) from comment #5)

Hi Chris, does M6c here mean, it should no longer block bug 1653457 (marked M6b) ?

M6c means fixing the bug soon (in September, ideally) is important, but it doesn't block our Fission Nightly experiment (October 6).

Neha moved bug 1653457 from M6b to M6c. This bug can stay in M6c.

Comment 7

[Chris Peterson [:cpeterson]]

(In reply to Chris Peterson [:cpeterson] from comment #6)

Neha moved bug 1653457 from M6b to M6c. This bug can stay in M6c.

Correction: Neha had moved a different xorigin meta bug (bug 1652554) from M6b to M6c.

I will move bug 1653457 from M6b to M6c now.

Comment 8

[Henri Sivonen (:hsivonen)]

Bug 1613054 wasn't sufficient for fixing this. The backout of bug 1649099 shows that the events being tested here don't fire deterministically. (I don't know why.)

Comment 9

[Edgar Chen [:edgar]]

I guess there might be some timing changes due to now parent window need to bounce an IPC message to the OOP iframe. I will take a look.

Comment 10

[Edgar Chen [:edgar]]

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

As for sync vs. async, I'm not yet sure where that part will settle.

window.focus() on a non-OOP iframe would call nsContentUtils::RequestFrameFocus synchronously, https://searchfox.org/mozilla-central/rev/7b07725fe9dc5d59a525990fc1dba78bc8b82af1/dom/base/nsGlobalWindowOuter.cpp#5143, and then dispatch focus event synchronously.

But window.focus() on an OOP iframe sends an IPC message to its parent frame instead, https://searchfox.org/mozilla-central/rev/7b07725fe9dc5d59a525990fc1dba78bc8b82af1/dom/base/nsGlobalWindowOuter.cpp#5131-5136, then wait for parent to send IPC back, the focus event is fired asynchronously due to the bounce of the IPC.

I also notice bug 1674702 that there is additional pair of blur and focus event gets fired while calling window.focus() on OOP iframe.

Comment 11

[Edgar Chen [:edgar]]

(In reply to Edgar Chen [:edgar] from comment #10)

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

As for sync vs. async, I'm not yet sure where that part will settle.

window.focus() on a non-OOP iframe would call nsContentUtils::RequestFrameFocus synchronously, https://searchfox.org/mozilla-central/rev/7b07725fe9dc5d59a525990fc1dba78bc8b82af1/dom/base/nsGlobalWindowOuter.cpp#5143, and then dispatch focus event synchronously.

But window.focus() on an OOP iframe sends an IPC message to its parent frame instead, https://searchfox.org/mozilla-central/rev/7b07725fe9dc5d59a525990fc1dba78bc8b82af1/dom/base/nsGlobalWindowOuter.cpp#5131-5136, then wait for parent to send IPC back, the focus event is fired asynchronously due to the bounce of the IPC.

Split this to bug 1674743.

Comment 12

[Edgar Chen [:edgar]]

Attachment: Bug 1660752 - Enable dom/events/test_bug238987.html on fission and cross-origin;

Comment 13

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/6d5a7637d34f
Enable dom/events/test_bug238987.html on fission and cross-origin; r=hsivonen

Comment 15

[Cristina Coroiu [:ccoroiu]]

https://hg.mozilla.org/mozilla-central/rev/6d5a7637d34f