Comment 14 for bug 1646166

Content script issues resolved by replacing our use of declarativeContent, which loads content scripts based on the content of the page, with a more traditional "content_scripts" configuration in the extension's manifest.json file. With content_scripts, we can configure the content script to be inserted before the DOM is rendered, ensuring it's always available to egHatch once loaded. Also, unlike declarativeContent, it loads consistently on windows/linux/mac.

Another side effect of this change is the user no longer has to interact with the extension to enable the permissions. They are enabled at extension install time.

I tested the new code on a variety of Chrome installs across OSes, with and without a google login. Broader testing required.