4 ms·
But won't they just follow google's changes, just like this one? They are more of the same. I'd be really surprised if they do anything different and major like
by NotSammyHagar 7y ago
But won't they just follow google's changes, just like this one? They are more of the same. I'd be really surprised if they do anything different and major like this.
- smileybarry 7y agoThey added Tracking Prevention a while back (which also blocks Google) and (so far) they haven't merged back some Chrome changes, like removing "reopen closed tab" from the per-tab context menu. Given Tracking Prevention I have faith they'll take a stand with webRequest.
- iggldiggl 7y agoI seem to remember hearing something somewhere that for the time being, Chrome might internally actually continue supporting blocking webRequest listeners for the sake of private extensions used within the context of enterprise deployments of Chrome. As long as that's true, maintaining a fork that allows blocking webRequest listeners for everybody should be comparatively easy. However the moment they are removing that feature for good and perhaps also start rewriting the network code, that's when things are going to be interesting for any forks that don't agree with that direction...