On Wed, Mar 16, 2022 at 10:41 AM Luca Greco <lgr...@mozilla.com
> TL;DR: We are preparing to deprecate the non-standard InstallTrigger global.
Thanks for taking this on! As the creator of this API all I can say is
"I'm sorry; it made sense at the time" (the original implementation is
long gone, maybe 2 or 3 times over).
> InstallTrigger is one of the historical ways extension developers could use to trigger the addon install flow from a website
The API even predated the concept of "addons" as we think of them
today--or even as we thought of them in Firefox 1.0! Initially it was
solving the problem of the need to ship and update Netscape 6 and the
Mozilla Suite in pieces, both to keep bandwidth down for people who
didn't need more than basic browsing (56K modems were the fast ones)
and because Netscape and the Mozilla Suite had different components.
For example, AOL management didn't want AIM in the open source Mozilla
Suite, and sure as heck didn't want the ChatZilla IRC client in the
Netscape version competing with its precious AIM. Even earlier,
cryptography export regulations meant the Mozilla Suite couldn't
contain the NSS source code, so users had to install/update the binary
"PSM" component after compiling the source.