Non-MPC extensions should not be disabled if e10s is disabled

RESOLVED WONTFIX

Status

()

Toolkit
Add-ons Manager
P5
normal
RESOLVED WONTFIX
6 months ago
4 months ago

People

(Reporter: Alice0775 White, Unassigned)

Tracking

({regression})

55 Branch
x86
Windows 10
regression
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: triaged)

Attachments

(1 attachment)

(Reporter)

Description

6 months ago
Firefox52esr works without problem.


Reproducible: always

Steps To Reproduce:
1. Make sure e10s is disabled
2. Install e10s incompatible legacy addon such as "DOM Inspector"


Actual Results:
The addon is automatically disabled.
No Restart now button display.

Expected Results:
A Restart now button should display.
(Reporter)

Comment 1

6 months ago
Created attachment 8872754 [details]
bug.png

Comment 2

6 months ago
You can work around this by flipping the preference extensions.allow-non-mpc-extensions.
Given that this only affects Nightly and it will change significantly in 57, this isn't a high priority.
Priority: -- → P5
Summary: E10s incompatible legacy addon is automatically disabled when newly install it even if e10s had been disabled → Non-MPC extensions should not be disabled if e10s is disabled
Whiteboard: triaged

Comment 3

4 months ago
Neither non-e10s Firefox nor non-multiprocessCompatible extensions are things we can spend any time on supporting.
Status: NEW → RESOLVED
Last Resolved: 4 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.