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

Chromium #896897 Manifest V3 breaking webRequest #3

Open
mfc opened this issue Jan 24, 2019 · 3 comments
Open

Chromium #896897 Manifest V3 breaking webRequest #3

mfc opened this issue Jan 24, 2019 · 3 comments
Labels
chrome help wanted Extra attention is needed high priority

Comments

@botherder botherder changed the title [tracking] chromium #896897 Manifest v3 web request changes - would break extension [tracking] Chromium #896897 Manifest V3 breaking webRequest Jul 24, 2019
@botherder botherder added chrome help wanted Extra attention is needed high priority labels Jul 24, 2019
@botherder
Copy link
Collaborator

As it stands, Manifest V3 changes seem to be confirmed and the initial beta rollout to be imminent. As it stands, the extension will be broken on Chrome and I currently do not see any way to workaround this.

To be verified: webmail integration should remain untouched.

@botherder
Copy link
Collaborator

In conversations with Google engineers, they suggested that in order to maintain the current functionality, a potential workaround would be to implement the blocking from within content scripts.

Currently it is not clear what will be the precise configuration for users' authorization of content scripts, because so far it seems as the users would be required to permit extensions to inject to each website manually. Obviously this would be a very disruptive user experience. This is not final, so it might change and possibly allow extensions to require users to manually authorize injection of content scripts on all websites.

That said, even this workaround seems less than optimal to me. I feel that blocking from content scripts would be a lot more aggressive and performance-impacting than through current webRequest. Additionally, this would definitely require the maintenance of two separate codebases, since we wouldn't want to do the same thing on Firefox, if Mozilla keeps webRequest as it is.

@mfc
Copy link
Author

mfc commented Sep 5, 2019

@botherder botherder changed the title [tracking] Chromium #896897 Manifest V3 breaking webRequest Chromium #896897 Manifest V3 breaking webRequest Jul 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chrome help wanted Extra attention is needed high priority
Projects
None yet
Development

No branches or pull requests

2 participants