If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Remove "New e10s window" option

RESOLVED FIXED in Firefox 40

Status

()

Firefox
General
RESOLVED FIXED
3 years ago
2 years ago

People

(Reporter: billm, Assigned: billm)

Tracking

34 Branch
Firefox 40
x86_64
Linux
Points:
---

Firefox Tracking Flags

(e10s+, firefox40 fixed)

Details

Attachments

(1 attachment)

(Assignee)

Description

3 years ago
If we remove this option, then the only way to get e10s is to enable it globally. That simplifies some things. It means that BrowserTabsRemoteAutostart() is a conservative check for whether e10s is in use.
tracking-e10s: --- → +
(Assignee)

Updated

3 years ago
Assignee: nobody → wmccloskey
(Assignee)

Comment 1

2 years ago
Created attachment 8598986 [details] [diff] [review]
patch
Attachment #8598986 - Flags: review?(felipc)
Comment on attachment 8598986 [details] [diff] [review]
patch

Review of attachment 8598986 [details] [diff] [review]:
-----------------------------------------------------------------

::: browser/base/content/browser-menubar.inc
@@ -30,5 @@
>  #ifdef E10S_TESTING_ONLY
> -                <menuitem id="menu_newRemoteWindow"
> -                          label="New e10s Window"
> -                          hidden="true"
> -                          command="Tools:RemoteWindow"/>

should also remove the Tools:RemoteWindow command, http://mxr.mozilla.org/mozilla-central/source/browser/base/content/browser-sets.inc#117
Attachment #8598986 - Flags: review?(felipc) → review+

Comment 3

2 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/d10105a75835
https://hg.mozilla.org/mozilla-central/rev/d10105a75835
Status: NEW → RESOLVED
Last Resolved: 2 years ago
status-firefox40: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 40
You need to log in before you can comment on or make changes to this bug.