Open Bug 1232395 Opened 9 years ago Updated 2 years ago

Console message that a11y disabled e10s is misleading when using force-enable

Categories

(Core :: Disability Access APIs, defect)

Product:
Core
Component:
Disability Access APIs
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
e10s - ---

People

(Reporter: quicksaver, Unassigned)

References

Details

After bug 1198459, enabling preference browser.tabs.remote.force-enable successfully forces e10s, but the console still says e10s is disabled:

> E10s has been blocked from running because: An accessibility tool is or was active. See bug 1198459.

From bug 1198459 comment 64 this is expected, but perhaps a follow-up message would be nice, as that message is misleading since e10s isn't actually blocked. Something like "E10s is running anyway, because you have force-enabled it in about:config."
tracking-e10s: --- → -
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.