Chrome Extension Manifest v3

[MichalVasut]

With latest update of Google Chrome (134.0.6998.35 (Official Build) (64-bit) ) the extension stopped working.

The page in extension store shows

This extension is no longer available because it doesn't follow best practices for Chrome extensions.

---

I'm guessing, it has something to do with Manifest v3: https://developer.chrome.com/docs/extensions/develop/migrate

[kav2k]

Indeed, that is the reason. Plus, it probably lacks privacy-related information in the store.
I will look into updating it this weekend.

[kav2k]

Because the window of opportunity to perform a migration with manifest v2 was missed, #63 not being solved in advance will mean settings will be wiped. Not a huge pain, but pain nonetheless.

[kav2k]

Nevermind, I can still access it in an offscreen document.

[kav2k]

So, it probably comes as no surprise that migrating mostly-8-years-old code to Manifest v3 is complicated.
It essentially requires a big rewrite of the code.

Bad news: it's not a coulpe-hours job.
Good news: I've started on it and intend to finish it.

Again, apologies that I missed all the deadlines on v3 migration, this work should've started at least half a year earlier.

[MichalVasut]

Don't worry about missed deadlines, happy to hear it'll get fixed. 😉

You've just followed golden rule - when it works, don't touch it. 😅

[kav2k]

Good start! Firefox's inability to run Webextensions in Service Workers actually gives me a good intermediate ground to experiment before I have to 100% commit to Chrome's v3 model.

Next steps:

• Replace XMLHttpRequest code with fetch()
• Rewrite code to use storage.local for both preferences and state information
• Write code to migrate old preferences to new storage
• Modernize the options page

[kav2k]

Busy time.. But slow progress ongoing. XMLHttpRequest is replaced with fetch()

[apallier]

Above all, thank you for this nice extension!
Is there an update on this issue?