Closed
Bug 1032977
Opened 10 years ago
Closed 10 years ago
With e10s enabled, we always load the first tab remote
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
e10s | ? | --- |
People
(Reporter: jimm, Unassigned)
References
Details
STR:
1) flip both remote prefs to true
2) Set your homepage to about:blank
3) restart the browser
result:
the first about:blank tab will be remote (with underlined title). Closing this tab and oening a new about:blank tab will shut down the plugin-container process and open the new tab locally.
Comment 1•10 years ago
|
||
jimm, vladikoff, mbrubeck and I chatted about this in IRC, and here's what we determined:
The inconsistency being noticed here is caused by the fact that the newtab page, when disabled, looks incredibly similar to about:blank. The difference, however, between about:blank and the disabled about:newtab is that about:blank is allowed to run in the content process. about:newtab is not remote-able just yet.
jimm had his newtab page disabled, and so when he opened a new tab, it looked like about:blank, but it wasn't remote - which looked inconsistent with the already-opened remote _real_ about:blank tab next to it.
This is working as expected - although jimm and I agree that about:blank probably doesn't need to ever be opened in a remote tab. That's a lot of machinery to rev up for a blank document.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•