Chromium #896897 Manifest V3 breaking webRequest

[mfc]

i saw you already replied to it but wanted to put it here to track any updates:

https://bugs.chromium.org/p/chromium/issues/detail?id=896897
https://groups.google.com/a/chromium.org/forum/#!topic/chromium-extensions/veJy9uAwS00
https://docs.google.com/document/d/1nPu6Wy4LWR66EFLeYInl3NzzhHzc-qnk4w4PX-0XMw8/edit
https://groups.google.com/a/chromium.org/forum/#!topic/chromium-extensions/WcZ42Iqon_M
https://discourse.mozilla.org/t/migrating-to-manifest-v3/35784/2
https://docs.google.com/document/d/1sKZFojq_fUusrebKsyNHfRk_9kpbIALFPS1Nvpddfs8/edit

[botherder]

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]

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]

Mozilla blogpost you shared: https://blog.mozilla.org/addons/2019/09/03/mozillas-manifest-v3-faq/