1167524 - Enabling multi-process Firefox Developer Edition seems to disable all addons

Status: RESOLVED INVALID

(Firefox :: Untriaged, defect)

Description

[Alex Heusingfeld]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:40.0) Gecko/20100101 Firefox/40.0
Build ID: 20150521004003

Steps to reproduce:

- Have Firefox Dev Edition installed on OS X 10.10.4 (14E17e)
- confirm update to FF Dev Edition 40.0a2
- confirm the request to enabling "Enable multi-process Firefox Developer Edition"


Actual results:

Enabling "Enable multi-process Firefox Developer Edition" seems to make the value of "xpinstall.signatures.required" indifferent (running Firefox Dev Edition 40.0a2) and sort of disables all(!!) my addons.


Expected results:

Enabling multi-process Firefox Developer Edition should not affect the extension signature check.

Comment 1

[Alex Heusingfeld]

Forget to mention that this originates from https://bugzilla.mozilla.org/show_bug.cgi?id=1047239#c10

Comment 2

[Dave Townsend [:mossop]]

(In reply to Alex Heusingfeld from comment #0)
> Enabling multi-process Firefox Developer Edition should not affect the
> extension signature check.

What makes you think that the signature checks are being affected here? What warning messages do you see in the add-ons manager for when multi-process is enabled and disabled?

Comment 3

[Alex Heusingfeld]

Attachment: Screenshot of FF dev edition's addons section showing all of the addons have a "Proceed with caution" warning.

This is a screenshot of Firefox developer edition's addons section after I checked the "Enable multi-process Firefox Developer Edition" checkbox in the settings and restarted Firefox. It shows all of the addons having a "Proceed with caution" warning though I set "xpinstall.signatures.required=false".

This at least affects the JSONView addon which should pretty-print JSON responses, but that doesn't happen.

Comment 4

[Tracy Walker [:tracy]]

Alex, does it work if you don't opt into e10s?

Comment 5

[Jonathan Howard]

The warning is new to firefox 40.0 it does not indicate addons are disabled. (shows both with and without e10s.)
xpinstall.signatures.required false is the aurora default. (will be false default on 40.0 beta and release.) The config option when true is for blocking(disabling) unsigned addons, it does not block the warning.

JSONView is incompatible with e10s (bug 1099976) I think your confusing the incompatibility bugs with disabled. Screenshot seems normal for 40+.

Comment 6

[Alex Heusingfeld]

When I uncheck "Enable multi-process Firefox Developer Edition" and restart, the addons are working as expected. What I cannot reproduce anymore is the state of the addons screen I had before I filed this bug. It was not showing the signature check warnings anymore for some installed addons. Now I get the same messages which I already attached.

Comment 7

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

Comment 5 looks correct to me, so I'm going to close this.

Even when xpinstall.signatures.required is false, we still display the warning for unsigned add-ons. However, the add-on is still enabled. You can see in your screenshot that JSONView, for example, is actually enabled since it has a "Disable" button next to it (not the best UI I have to say).

The reason JSONView doesn't work for you is that it's incompatible with e10s. That's separate from the signing issue though.