Skip to content
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

Bug: This extension may soon no longer be supported #1256

Closed
probonopd opened this issue Aug 13, 2024 · 3 comments
Closed

Bug: This extension may soon no longer be supported #1256

probonopd opened this issue Aug 13, 2024 · 3 comments

Comments

@probonopd
Copy link

probonopd commented Aug 13, 2024

Describe the bug

One of the most popular extensions, uBlock Origin, triggers a strange message (screenshot below), saying "This extension may soon no longer be supported".

Apparently this has to do with the the phasing out of "MV2 extensions", whatever that is.

So please do NOT phase out "MV2 extensions" because they are essential to an advertising-free web.

To Reproduce

uBlockOrigin/uBlock-issues#3309

Expected behavior

uBlock Origin works like it always has.

Screenshots

image

Notes

@oliverdunk
Copy link
Member

Hi @probonopd - you can learn more about Manifest V3 and our plans for the MV2 deprecation here: https://developer.chrome.com/blog/resuming-the-transition-to-mv3. If you haven't found it already, there are some alternatives you can consider migrating to, like uBlock Origin Lite published by the same author.

I'm going to close this issue since this issue tracker is for our code samples, but I hope this helps.

@oliverdunk oliverdunk closed this as not planned Won't fix, can't repro, duplicate, stale Aug 13, 2024
@probonopd
Copy link
Author

probonopd commented Aug 13, 2024

Thanks @oliverdunk. The question is, where at Google can we (the users) make our voices heard in a productive way that we*d appreciate MV2 not being deprecated? So that Product Management can overthink their decisions.

@oliverdunk
Copy link
Member

oliverdunk commented Aug 14, 2024

We've been working with developers on this change for several years now, and we've received a lot of feedback already. We still think this is the best direction so it's very unlikely we will make significant changes to the rollout plan at this point. Unfortunately, I don't have a specific channel I can point you towards but we'll keep looking at the various developer support channels we have to identify gaps in capabilities and in order to find new features to add to the platform.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants