Closed Bug 1364492 Opened 7 years ago Closed 7 years ago

Allow not multiprocess compatible extensions to be activated when add-on compatibility checking is deactivated

Categories

(Firefox :: Extension Compatibility, defect)

Product:
Firefox
Component:
Extension Compatibility
Version:
55 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: BesTo, Unassigned)

References

(
URL
)

Details

IMHO, when add-on compatibility checking is deactivated, there should be a way to activate not multiprocess compatible extensions, too.
I'm running FF55.0a1, 64bit, E10s and after auto-deactivating all not multiprocess compatible extensions the most of my extensions now deactivated. There are IMHO ATM to much extensions on AMO that are not multiprocess compatible and auto-deactivating all makes life of alpha testers ATM to hard.

Overall reports from https://arewee10syet.com/:
compatible 		1,229
compatible-webextension 2,309
unknown 		16,841
undefined 		43
incompatible 		45
The preference extensions.allow-non-mpc-extensions lets you toggle that behavior on Nightly.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.