1377148 - New windows are not isolated

Status: RESOLVED INVALID

(Core :: General, enhancement)

Description

[ashley]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce:

Visit this URL: https://www.scirra.com/labs/bugs/popup-isolation/

Try each of the four options to open a new tab/window. In the window that opens, click the "hang" button to hang for 3 seconds. Check if this action affects the original window.


Actual results:

In every case, the main thread is shared with the parent window, so clicking the button causes the parent window to freeze as well.


Expected results:

There should be isolation in at least some of these cases. At least the rel=noopener link, and the cross-origin popup window, should not be able to have any impact on the parent window.

Chrome only isolates the rel=noopener case - I filed a bug for isolating the cross-origin popup case at crbug.com/738046. Edge does well on this and manages to isolate all four cases!

Comment 1

[Daniel Veditz [:dveditz]]

How browsers allocate threads/processes to web content is not specified in any standard. Your "Expected" result is more of a "Desired" result, but the reality depends on how the browser is implemented.

Not sure where to file this, but it's not "DOM: Security". Some architecture component?

Comment 2

[Justin [:JW_SoftvisionQA]]

I can reproduce this issue on Mozilla/5.0 (Windows NT 10.0; WOW64; rv:56.0) Gecko/20100101 Firefox/56.0

I am thinking this is an e10s issue? I am not 100% sure.

Comment 3

[Selena Deckelmann :selenamarie :selena]

Jim - where should something like this live?

Comment 4

[Jim Mathies [:jimm]]

(In reply to ashley from comment #0)
> User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
> (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36
> 
> Steps to reproduce:
> 
> Visit this URL: https://www.scirra.com/labs/bugs/popup-isolation/
> 
> Try each of the four options to open a new tab/window. In the window that
> opens, click the "hang" button to hang for 3 seconds. Check if this action
> affects the original window.
> 
> 
> Actual results:
> 
> In every case, the main thread is shared with the parent window, so clicking
> the button causes the parent window to freeze as well.

Good site isolation can be had by simply bumping up your processCount pref. I have about 15 tabs open and the "hang" button didn't jank any other tab in my browser.

We'll be working on improving site isolation over time through various projects. This bug is not actionable on it's own, although it does have a good test case for qa.

Comment 5

[ashley]

The default process count appears to be 4, and if the only Firefox window I have open is the repro URL, the popup still hangs the parent window. I tested the latest Nightly.

Do I need to increase the process count above 4 to have 2 windows isolated? If so, how come? If not, is it still a bug?

Comment 6

[Firefox Bug Husbandry Bot]

Moving from Core::Untriaged to Core::General https://bugzilla.mozilla.org/show_bug.cgi?id=1407598