Closed
Bug 1009030
Opened 11 years ago
Closed 11 years ago
[e10s] e10s window is restored as normal window
Categories
(Firefox :: Session Restore, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: alice0775, Unassigned)
References
(Blocks 1 open bug)
Details
Build Identifier: https://hg.mozilla.org/mozilla-central/rev/20ca234fd62b Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0 ID:20140512030202 STR: 1. open browser with layers.offmainthreadcomposition.enabled = true 2. open new e10s window and open some web pages 3. Exit browser 4. Start browser and click "Restore Previous Session" Actual Results: All window is normal window(not e10s). (no underline in tab title.) Expected Results e10s window should be restored as e10s window
Comment 1•11 years ago
|
||
I don't think we should spend time on making that work. The "open new e10s window" is just a nice feature to kick off doogfooding better but if you really want your tabs restored as "remote" you should probably just be running in e10s mode.
I agree. This is the behavior we expect.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Thanks for the report though! They're always appreciated :-).
Comment 4•11 years ago
|
||
FWIW I like running in mix mode and this annoys me when doing manual testing. My workflow looks like this: - Close browser with e10s with my test case - Edit, recompile, run - Non e10s tab running my test case is restored - Sometimes accidentally test with my test case while I forget it's no longer running remote. - Close my testcase running without e10s - Open e10s window manually (no shortcut key) - Go to test case
If you're testing a lot with e10s, I would recommend doing it in a profile where browser.tabs.remote.autostart is set. That way, all your tabs will be restored as remote. It's also more convenient not to have to ask for an e10s window in the first place.
Comment 6•11 years ago
|
||
Thanks for the tip, I'll try that. But I still feel like this would promote nightly users testing e10s more.
You need to log in
before you can comment on or make changes to this bug.
Description
•