-
-
Notifications
You must be signed in to change notification settings - Fork 472
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to Manifest V3 #1821
Comments
Some API changes are needed for manifest upgrade, see Migrate chrome extension from manifest v2 to v3: How to update these APIs? - Stack Overflow. |
I had looked into this, now the blocker is that background service worker just cannot start, it remains Looks like the bug just got fixed 4 days ago, will try that again after the fix released. |
Pending on w3c/webextensions#279 (comment) |
This deadline is quickly approaching. The new dates are,
|
@brookhong @b0o Appreciate it if the team could share insights on the current state. Thanks! |
I myself don’t have any new info, and unfortunately I currently don’t have the bandwidth to work on this. |
I believe the Chrome team pushed back these dates indefinitely. That’s not to say deprecation won’t happen, but there are no official dates as far as I can tell.
https://developer.chrome.com/docs/extensions/migrating/mv2-sunset/ |
@b0o Thank you for the update |
I don't read that the same way, so be cautious here. Those are the updated deadlines as I understand it, and as reported by third parties. From the article titled, "Google delays execution of doomed Chrome extensions"
https://www.theregister.com/2022/09/30/google_manifestv3_chrome_extensions/ |
@EvanCarroll That article is dated 30 Sep 2022, it's about the first time Google delayed MV3. They later delayed it again, here is an article dated 01 Apr 2023:
— Google halts purge of legacy Chrome Extensions, again • The Register That article is based on this post on Google Groups:
— https://groups.google.com/a/chromium.org/g/chromium-extensions/c/zQ77HkGmK9E/m/HjaaCIG-BQAJ (If you're interested in this I recommend subscribing to that thread) As far as I know, there haven't been any additional updates, so I think it should be at least 6+ months away. That's also what the official sunset page says:
— https://developer.chrome.com/docs/extensions/migrating/mv2-sunset/ |
Thanks, that Mar 29th post is certainly the newest so I'm convinced. Talk about a butchered roll out. They really googled that one up. |
Yes, google must have delayed this again. As for this extension, I had created a branch https://github.com/brookhong/Surfingkeys/tree/mv3 last December, it roughly works(I haven't verified every function), so MV3 should not be a big problem as long as a string parameter I check w3c/webextensions#279 (comment) occasionally, there is no update this year except more and more extensions coming and requesting for the same support. |
@brookhong I submitted a formal proposal for it. They should hopefully discuss it next Thursday. |
Another update from Google: https://developer.chrome.com/blog/resuming-the-transition-to-mv3/ |
It's unknown whether the userScripts.execute() method will be supported before the deadline, or even at all. Chrome suggests using a wrapped userScript approach for now. This means adding a userScript that applies to all relevant URLs. The code should be wrapped in a function. You will call that function when needed using window.postMessage and window.onMessage. |
@newRoland I don't know the full architecture. With this workaround, what are we losing? |
Thanks @b0o for dropping the link. This is such a botched migration. Google needs help, badly. Here is the tldr of this release, Google will be disabling v2 in Dev, Canary, and Beta in June 2024, and they'll adapt that to stifle backlash until they're comfortable and then at some undetermined point they intend to graduate that functionality to production, in stages. So with the branch and work already done in some form, I think this project just holds off until June. |
@asknet Surfingkeys allows users to execute user scripts. No loss if you migrate and use the wrapped userScript approach to maintain this feature. The wrapped userScript approach needs to be implemented with care as it's performance isn't great. The user script should be scoped to a particular website because you're pretty much pre-loading. If not scoped to a particular URL, you're pretty much loading it on all websites, even if it's irrelevant and will never be called. |
I have a great update! It looks like the proposal is moving forward. |
Heya folks, sorry, it's not clear to me what's supposed to be happening next. The proposal linked above seems to have been merged a few months ago, what are the next steps here? Really would be sad if I was suddenly unable to use Surfingkeys 😅 |
I have been working on this for some while, here are some updates
|
— gkzhb on #1445 (comment)
Bolding mine - need to investigate this claim that V3 will break the ability to execute user scripts.
— aspiers on #1445 (comment)
Update 09/28/22
MV2 deprecation in Chrome Stable has been postponed until June 2023.
See: More details on the transition to Manifest V3
The text was updated successfully, but these errors were encountered: