Wanted: Migrating Chrome extension Manifest V2 to V3

[sinsinpub]

According Google's timeline, we have 1 year remaining to migrate Manifest v2 to v3 if we gonna let our extension accepted by future Chrome and released to webstore. (https://developer.chrome.com/docs/extensions/mv3/mv2-sunset/)

Methods they introduced: https://developer.chrome.com/docs/extensions/mv3/intro/mv3-migration/
TODO Checklist accordingly:

• Rework on background pages (to be evaluated)
• Replace chrome.webRequest with chrome.declarativeNetRequest (gakada may finish it?)
• Update host permissions (easy modification)
• Update browser_action (easy modification)
• Update content_security_policy (docs reviewing needed)
• Update web_accessible_resources (docs reviewing needed)
• Replace deprecated API: chrome.extension.getURL() (others not found?)

I guess the most hard part is the one that rewriting background scripts with service workers.
chrome.webRequest only affects the Gadget Block Bypass requests redirection.

However, because Manifest V3 is available beginning with Chrome 88, and I'm still using Chromium 60, so basically I will not be able to test v3 continuously. More developers & testers are wanted to complete this task thank to google guys. The bottom line is Dec 2022.

I will make a new branch (perhaps named manifest-v3) to develop and test v3, and keep a forked v2 branch for guys (including me) to use old chrome versions.