Closed
Bug 1306135
Opened 8 years ago
Closed 8 years ago
Since Firefox 49.0.1 Release If i install a new addon (XPI) for the first time after an update, I get a modal to restart the browser in order to enable the XPI
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: look4deepak, Unassigned)
Details
Attachments
(1 file)
35.13 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 Steps to reproduce: 1. Update Firefox to 49.0.1 2. Make sure you do not have any addon installed previously 3. Go to Mozilla addon store and add any addon for my example I used https://addons.mozilla.org/en-US/firefox/addon/firebug/?src=search Actual results: Users are prompted to restart Firefox in order to enable addon Expected results: Users should not be asked to restart Firefox to enable addon. Please note that it only happens the first time after update, any consecutive addon installs work fine.
I don't think Firebug is a restartless add-on.
Component: Untriaged → Add-ons Manager
Product: Firefox → Toolkit
(In reply to Loic from comment #1) > I don't think Firebug is a restartless add-on. I tested it on older version of Firefox 47 and 48 and it gets installed without asking to restart firefox. Also, I am seeing this "restart" behavior for all addons, I used Firebug as an example as it is one of the featured addons.
Comment 3•8 years ago
|
||
Did you try this in a fresh profile? In Firefox 49, multiprocess is enabled by default (if no add-ons are installed). If you install an add-on that does not support multiprocess, Firefox needs to restart in order to disable multiprocess so the add-on works.
Flags: needinfo?(look4deepak)
(In reply to Andreas Wagner [:TheOne] from comment #3) > Did you try this in a fresh profile? > In Firefox 49, multiprocess is enabled by default (if no add-ons are > installed). If you install an add-on that does not support multiprocess, > Firefox needs to restart in order to disable multiprocess so the add-on > works. I tried it with XPI that is compatible with multiprocess with fresh profile, but I see the similar behavior where Firefox needs to be restarted.
Comment 5•8 years ago
|
||
In 49, only a handful of add-ons are enabled to work on e10s, regardless of their compatibility as we are slowly scaling e10s for complete rollout.
Updated•8 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Updated•8 years ago
|
Flags: needinfo?(look4deepak)
(In reply to Andreas Wagner [:TheOne] from comment #5) > In 49, only a handful of add-ons are enabled to work on e10s, regardless of > their compatibility as we are slowly scaling e10s for complete rollout. Thanks,Is there a way for me to get my extension approved in e10 (beta/test) so that I confirm that everything is working fine. I am assuming I can test with upcoming nightly builds. Any info in this regards will be helpful
Comment 7•8 years ago
|
||
Starting with Firefox 50, all add-ons that are marked as compatible with e10s and all webextensions are using e10s by default. You can test on the beta channel: https://www.mozilla.org/en-US/firefox/channel/
(In reply to Andreas Wagner [:TheOne] from comment #7) > Starting with Firefox 50, all add-ons that are marked as compatible with > e10s and all webextensions are using e10s by default. > > You can test on the beta channel: > https://www.mozilla.org/en-US/firefox/channel/ Thanks!
(In reply to Deepak from comment #8) > (In reply to Andreas Wagner [:TheOne] from comment #7) > > Starting with Firefox 50, all add-ons that are marked as compatible with > > e10s and all webextensions are using e10s by default. > > > > You can test on the beta channel: > > https://www.mozilla.org/en-US/firefox/channel/ > I installed 50.0b3 from the beta channel and noticed that installing add-on with multi-purpose support still require browser to be restarted. As a end goal I am trying to see how to build a restartless extension, and I can't use webextensions as all the APIs that i need are not ready yet.
Comment 10•8 years ago
|
||
Which add-on did you test with?
Reporter | ||
Comment 11•8 years ago
|
||
(In reply to Andreas Wagner [:TheOne] from comment #10) > Which add-on did you test with? Thanks Andreas for the help. I was testing the wrong add-on.
You need to log in
before you can comment on or make changes to this bug.
Description
•