Let's try to make background.js a completely generic file, which relies on declarative specification, by the extension, of its contents, and loads it.
This will hinge on getting data from the package manifest, in manifest.json
This should have three phases:
Make the manifest usable in background.js
Use the manifest to obtain/generate non-tabular data, like the options dialog URI and the default pref file path
Use the manifest to obtain/generate the tabular data passed to WindowsListener: The per-window overlay injectors, and the Chrome URLs for registration. That means the tables will go into the manifest.json, in some form or another - or alternative, will be generated from inspecting package files and directories.
Once this is done, we might take a crack at dropping the overlay injectors altogether and making that part declarative as well.
Let's try to make
background.jsa completely generic file, which relies on declarative specification, by the extension, of its contents, and loads it.This will hinge on getting data from the package manifest, in
manifest.jsonThis should have three phases:
background.jsOnce this is done, we might take a crack at dropping the overlay injectors altogether and making that part declarative as well.
Anyway, this bug is about phases (1.) and (2.)