[ghostwords]

>Ideally, I'd like to see MV3 continue supporting the persistent context use case as well as maintaining webRequest blocking support.

Same, which is why I engage with browser representatives in the W3C WebExtensions Community Group.

Unfortunately, the status quo is grim with Firefox seemingly uninterested in standing up to Chrome and citing compatibility as the main reason for following Chrome into mandatory Service Workers.

[smaddock]

I appreciate that yourself and other folks are engaging in the community to request improvements.

Prior to the group being formed, most discussion regarding MV3 occurred on the Chrome Extensions Google Group [0]. While feedback was accepted and open there, I hadn't seen the Chrome team acting on it to make changes. That's where most of my pessimism on the situation comes from.

I believe the Chrome team's main motivation is removing any functionality in MV3 which would have the possibility of reducing performance in normal browsing. I personally don't have much hope that they'll be backpedaling on any changes.

[0] https://groups.google.com/a/chromium.org/g/chromium-extensio...

[ghostwords]

Remember the Chrome "puzzle piece" extensions menu post where Google announced hiding extension icons inside their new menu by default?

https://groups.google.com/a/chromium.org/g/chromium-extensio...

Almost universally negative feedback and ... "Thank you for the feedback", we're not changing anything.

https://bugs.chromium.org/p/chromium/issues/detail?id=111474...