Update to Manifest V3

[ChrisNZL]

Fauxbar 1.8.1 uses Manifest V2.

Google will be enforcing Chromium Manifest V3 for extensions in the future:

There are two key dates for the phase-out:

• January 17, 2022: New Manifest V2 extensions will no longer be accepted by the Chrome Web Store. Developers may still push updates to existing Manifest V2 extensions, but no new Manifest V2 items may be submitted.

• January 2023: The Chrome browser will no longer run Manifest V2 extensions. Developers may no longer push updates to existing Manifest V2 extensions.

---

Reading:

• https://blog.shahednasser.com/chrome-extension-tutorial-migrating-to-manifest-v3-from-v2/
• https://developer.chrome.com/docs/extensions/mv3/intro/mv3-migration/
• https://developer.chrome.com/docs/extensions/reference/
• https://developer.chrome.com/docs/extensions/mv3/intro/mv3-overview/
• Chromium Issue 104102: Create a new API permission for access to favicons

Service workers

• https://stackoverflow.com/questions/66406672/chrome-extension-mv3-modularize-service-worker-js-file
• https://developer.chrome.com/docs/extensions/mv3/migrating_to_service_workers/
• https://stackoverflow.com/questions/66055882/chrome-extensions-use-the-background-service-worker-key-instead-manifest-vers

favicons

Permissions for chrome://favicon/* is no longer allowed. Upcoming favicon API is not implemented into Chrome yet.

Chromium Issue 104102: Create a new API permission for access to favicons

Suggestion to use https://www.google.com/s2/favicons?sz={size}&domain_url={url} for now, eg:

https://www.google.com/s2/favicons?sz=32&domain_url=https://www.stuff.co.nz/

Other nice-to-haves (though low priority)

• Link to chrome://whats-new/ in the Fauxbar > Chrome menu
• Add a Sessions list in the Fauxbar menu -- use chrome.sessions API
• See if an inline script can take focus from Omnibox without needing to close the tab: https://stackoverflow.com/a/71424805/206410

[ChrisNZL]

Update on favicons

Possibly finally fixed; https://bugs.chromium.org/p/chromium/issues/detail?id=104102#c59

Need to experiment to see if it works in Chrome Canary, and then watch for when it hits Chrome Stable.

(currently, Chrome Stable is version 102, and Canary is 104...)

TODO:

• Update Fauxbar's manifest to whatever minimum Chrome version this favicon fix makes it to.