I seem to remember hearing something somewhere that for the time being, Chrome might internally actually continue supporting blocking webRequest listeners for t

I 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...