2007792 - Make our code in interventions.js start up as synchronously as possible.

Status: ASSIGNED

(Web Compatibility :: Interventions, enhancement)

Description

[Thomas Wisniewski [:twisniewski]]

After the changes I'm making in bug 2007409, we can refactor interventions.js to make it start up with essentially no async code (just the registration of content scripts). This is a pretty big deal, since it will let us register our webRequest listeners early enough that they will all end up persisted, which they are not right now (as per bug 2007607 comment 3). While we're at it, we can fix a few minor bugs with about:compat when prefs are toggled, clean up our logging a little so it's less spammy, and remove our setPref API (since it needs to be async, and we don't really need it.

This refactor will also open the door to further optimizations, for instance only registering a single listener per webRequest events (which could further help startup perf on slower devices), as well as making it much easier to begin persisting our listeners and content scripts across add-on restarts.

Comment 1

[Thomas Wisniewski [:twisniewski]]

Attachment: Bug 2007792 - Make our code in interventions.js start up as synchronously as possible; r?denschub