Let non-core providers determine whether a restart is needed on startup, via checkForChanges()

RESOLVED WONTFIX

Status

()

RESOLVED WONTFIX
9 years ago
6 months ago

People

(Reporter: Unfocused, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [rewrite])

Currently, only core providers (those hardcoded into the PROVIDERS array in AddonsManager.jsm) get the chance to determine whether a restart is needed on startup (via a call to provieder.checkForChanges). Ideally, non-core providers would be able to do this also. This would require loading them early enough in the startup sequence - presumably by adding a way for providers to (optionally) be XPCOM components that can be discovered and automatically loaded.
Yeah I'm thinking of using the category manager as a way to register services and jsms that provide providers.

I think in general we should split providers into those that need to be loaded at startup and those that only need to be loaded later.

Comment 2

9 years ago
I still have semi-solid plans related to e10s which would allow us to completely avoid restarting: what's the motivation for exposing the undesirable restart-required behavior to non-core code?
(In reply to comment #2)
> I still have semi-solid plans related to e10s which would allow us to
> completely avoid restarting: what's the motivation for exposing the undesirable
> restart-required behavior to non-core code?

Probably none if we can stop restarts altogether. Do you have notes anywhere on your plans?

Comment 4

6 months ago
non-core providers is not something that is supported these days
Status: NEW → RESOLVED
Last Resolved: 6 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.