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

RESOLVED WORKSFORME

Status

()

RESOLVED WORKSFORME
a year ago
a year ago

People

(Reporter: BesTo, Unassigned)

Tracking

55 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

a year ago
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
Last Resolved: a year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.