1938456 - Add glue to allow newtab to be packaged as a built-in addon

Status: ASSIGNED

(Firefox :: New Tab Page, task)

Description

[Mike Conley (:mconley) (:⚙️)]

The manifest should supply the bare minimum to let the built-in add-on be registered, and to allow it to have privileged code run via the experimental_api mechanism.

Comment 1

[Mike Conley (:mconley) (:⚙️)]

This will also add some scripts to do basic resource mapping and prevent runtime updates.

Comment 2

[Mike Conley (:mconley) (:⚙️)]

Attachment: Bug 1938456 - Add built-in addon glue code to newtab. r?pdahiya!,baku!

This is based on the patches from bug 1938155. This patch makes it so that
if ac_add_options --browser-newtab-as-addon is set in your mozconfig, then
the New Tab code will be packaged as a built-in addon.

Flipping that flag to enabled requires a full-build in order to rebuild
the built_in_addons.json file at build time.

You might find upon flipping the enabled flag the first time that the
initial about:home and a few about:newtab's will not load. This is
due to a race right now between the New Tab built-in addon and the
about:home startup cache. That's covered by bug 1946569.