1579847 - Pop-up blocker doesn't work with fission with window.open being called from a remote subframe.

Status: RESOLVED DUPLICATE of bug 1646539

(Core :: DOM: Core & HTML, defect, P3)

Comment 1

[Andreas Farre [:farre]]

Attachment: index.html

Comment 2

[Andreas Farre [:farre]]

Attachment: frame.html

Comment 3

[Andreas Farre [:farre]]

Attachment: content.html

Comment 4

[Andreas Farre [:farre]]

STR:
Serving index.html and content.html from:

web-platform.test:8000

and frame from not-web-platform.test:8000.

Make sure that pop-ups for not-web-platform.test/web-platform.test is not allowed, and that fission.autostart is turned on before first load.

Expected:
Allow pop-up hanger, and if pop ups allowed, then a popup.

Actual:
No pop-up blocker hanger

Comment 5

[Andreas Farre [:farre]]

One reason for the failure is found in nsGlobalWindowOuter::PopupWhitelisted() that does nsGlobalWindowOuter traversal using GetInProcessParent.

Comment 6

[Chris Peterson [:cpeterson]]

Tentatively moving all bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to the "?" triage milestone.

This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:

0ee3c76a-bc79-4eb2-8d12-05dc0b68e732

Comment 7

[Chris Peterson [:cpeterson]]

Tracking for Fission Nightly (M6)

depends on WindowContext bug 1583863

Comment 8

[Chris Peterson [:cpeterson]]

Andreas, can you work on this bug after you finish your current bugs? You filed this bug and you wrote WindowContext. :)

Tracking for Fission Nightly M6b

Comment 9

[Andreas Farre [:farre]]

Sure thing.

Comment 11

[Chris Peterson [:cpeterson]]

Clearing Fission Milestone for bugs resolved as duplicates. We don't need to track duplicates.