Will this hack continue to work when MV2 is fully removed in the next Chrome version? Or will the webRequestBlocking APIs remain for forceinstalled extensions?
As far as I know, Google is not planning on removing webRequestBlocking for forceinstalled extensions. I assume it's because of school/enterprise network filtering extensions effectively requiring it to function.
Chromium DevTools are much better in my opinion and switching browsers for development is too much of a hassle for me. Even if I was able to get used to Firefox DevTools, multiple of the projects I built and maintain ([1] [2]) require Web APIs that Firefox opposes because they believe the user cannot handle permissions dialogs (see File System Access API and WebUSB), so I would have to switch browsers anyway.
I also have had scrolling performance issues and jitter (which have been reported multiple times to the bug tracker by others already) on pages as simple as the Mozilla bug tracker, which is unusable for me.
I see no reason to switch to an objectively worse browser on my machines (lack of web features I use, performance issues on not-YouTube) when I know that there are multiple escape hatches allowing me to continue using chromium: porting uBO to mv3, or using a chromium fork that keeps mv2 enabled.
Will this hack continue to work when MV2 is fully removed in the next Chrome version? Or will the webRequestBlocking APIs remain for forceinstalled extensions?
As far as I know, Google is not planning on removing webRequestBlocking for forceinstalled extensions. I assume it's because of school/enterprise network filtering extensions effectively requiring it to function.
Why not just switch to Firefox?
Chromium DevTools are much better in my opinion and switching browsers for development is too much of a hassle for me. Even if I was able to get used to Firefox DevTools, multiple of the projects I built and maintain ([1] [2]) require Web APIs that Firefox opposes because they believe the user cannot handle permissions dialogs (see File System Access API and WebUSB), so I would have to switch browsers anyway.
I also have had scrolling performance issues and jitter (which have been reported multiple times to the bug tracker by others already) on pages as simple as the Mozilla bug tracker, which is unusable for me.
I see no reason to switch to an objectively worse browser on my machines (lack of web features I use, performance issues on not-YouTube) when I know that there are multiple escape hatches allowing me to continue using chromium: porting uBO to mv3, or using a chromium fork that keeps mv2 enabled.
[1]: https://celeste.r58playz.dev/
[2]: https://terraria.r58playz.dev/