1725902 - chrome.webNavigation.onCommitted is not triggered when disable E10S

Status: RESOLVED WONTFIX

(WebExtensions :: General, defect)

Description

[bin li]

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

Steps to reproduce:

I use the Firefox 90 and Firefox 91.
1, change the Firefox to single process mode(disable the E10S)
2, load a simple web extension, which just contains the following code in background:
function onWebCommitted(details) {
console.log("&&&& onWebCommitted, url: " + details.url)
}

function onBeforeNavigate(details) {
console.log("&&&& onBeforeNavigates, url: " + details.url)
}

chrome.webNavigation.onCommitted.addListener(onWebCommitted);
chrome.webNavigation.onBeforeNavigate.addListener(onBeforeNavigate);

3, navigate to any websites

Actual results:

There should some logs like following:
&&&& onBeforeNavigates, url:............
&&&& onWebCommitted, url:..............

But in in single process there are only onBeforeNavigates logs, looks like the chrome.webNavigation.onCommitted callback wasn't be called.
But for some internal pages(webconsole/index.html, about:blank.....) it will be called, only the public sites have issues.

Expected results:

the chrome.webNavigation.onCommitted should be called in single process mode(disable e10S)

Comment 1

[bin li]

Attachment: ff90.png

we can see there's no onWebCommitted log for url https://www.wikipedia.org/, but have for url about:blank and webconsole/index.html.

Comment 2

[:Gijs (he/him)]

(In reply to bin li from comment #0)

I use the Firefox 90 and Firefox 91.
1, change the Firefox to single process mode(disable the E10S)

This isn't supported. Why are you trying to do it? It's a bad idea. Also, how are you doing it?

Also, why did you file this as a security issue?

Comment 3

[bin li]

(In reply to :Gijs (he/him) from comment #2)

(In reply to bin li from comment #0)

I use the Firefox 90 and Firefox 91.
1, change the Firefox to single process mode(disable the E10S)

This isn't supported. Why are you trying to do it? It's a bad idea. Also, how are you doing it?

Also, why did you file this as a security issue?

Sorry, my mistake, I didn't notice I make it as a security issue, sorry for the inconvenience...
But do you mean the single process is not supported any more? Currently the product I'm working on is using Firefox with single process as testing tool, if the single process is not supported in the future, it will have big impact on us.

Comment 4

[:Gijs (he/him)]

(In reply to bin li from comment #3)

But do you mean the single process is not supported any more?

It's certainly not "officially supported". It isn't possible to easily run Firefox this way, and hasn't been for a while. I'm still curious how you're doing it - rebuilding Firefox, or setting the environment variable, or something else?

Currently the product I'm working on is using Firefox with single process as testing tool, if the single process is not supported in the future, it will have big impact on us.

If you want to use Firefox to test things, I'd recommend using webdriver, which works fine with multi-process Firefox.

Comment 5

[Kris Maglione [:kmag]]

(In reply to bin li from comment #3)

But do you mean the single process is not supported any more? Currently the product I'm working on is using Firefox with single process as testing tool, if the single process is not supported in the future, it will have big impact on us.

It isn't supported in the present.

Comment 6

[bin li]

(In reply to :Gijs (he/him) from comment #4)

(In reply to bin li from comment #3)

But do you mean the single process is not supported any more?

It's certainly not "officially supported". It isn't possible to easily run Firefox this way, and hasn't been for a while. I'm still curious how you're doing it - rebuilding Firefox, or setting the environment variable, or something else?

Currently the product I'm working on is using Firefox with single process as testing tool, if the single process is not supported in the future, it will have big impact on us.

If you want to use Firefox to test things, I'd recommend using webdriver, which works fine with multi-process Firefox.

Hi Gijs, for official FF, I set a environment(MOZ_FORCE_DISABLE_E10S) to disable the E10S, also I have a customized version FF that rebuild by my self, for this version I disable the E10S by setting a preferences(browser.tabs.remote.autostart).
Thanks.

Comment 7

[bin li]

(In reply to Kris Maglione [:kmag] from comment #5)

(In reply to bin li from comment #3)

But do you mean the single process is not supported any more? Currently the product I'm working on is using Firefox with single process as testing tool, if the single process is not supported in the future, it will have big impact on us.

It isn't supported in the present.

Hi Kris, thanks for you reply. I saw this defect is set to won't fix, it really not a good news for us...
However, I have already found the commit that cause this issue, I will try to find a workaround, thanks.

Comment 8

[Tomislav Jovanovic :zombie]

Can you describe why you need to run in non-e10s mode, perhaps we could suggest a different solution.