-
Notifications
You must be signed in to change notification settings - Fork 54
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
Is this an attempt to force everybody to implement the controversial Manifest V3? #5
Comments
Thank you |
Maybe out of topic. I investigate Manifest V3 support in our extension and found the Chrome implementation has many bugs/un-features that block us. |
@Jack-Works, that is off topic ;) I'd encourage you to create bugs on the Chromium issue tracker or discuss the issues you're encountering on either the chromium-extensions group or on Stack Overflow. |
Yeah, I did. But after one year there is no progress on those issues I had. |
Based on my reading of the W3C's Design Principals and Manifest v3 design goals, Manifest v3 is not consistent with the W3C. The conflict arises because the W3C puts the user first as stated in Priorities of Constituencies. However, Manifest v3 puts the website operator and website first. Manifest v3 should be categorically rejected by the W3C. If Google wishes to privately pursue its agenda, then that is Ok. Organizations are welcomed to side-load a modified browser that implements Manifest v3. Organizations are free to do what they want. |
Is this an attempt to force everybody to implement the controversial Manifest V3 and kill off ad blockers such as uBlock Origin?
The text was updated successfully, but these errors were encountered: