4 ms·
While they're interested in maintaining compatibility with Chrome's v3, there's no standard that forces them to make every single v3 change Chrome does. v2 als
by input_sh 5y ago
While they're interested in maintaining compatibility with Chrome's v3, there's no standard that forces them to make every single v3 change Chrome does.
v2 also already differs in some ways in which Firefox thinks it makes sense. I'm not scared at all that they're gonna deprecate webRequest.BlockingResponse in favour of declarativeNetRequest, which is the specific API function that adblockers rely on. After all, that function has nothing to do with security, best you could argue is that it's related to performance due to filter lists becoming absurdly long.
- dotancohen 5y agoIn the context of `webRequest.BlockingResponse` being a performance bottleneck due to filter lists becoming absurdly long, it does in fact become a security issue. Filter lists are as long as they are because that is the amount of domains that have demonstrated an interest in harming our security (and for many people, online privacy _is_ physical security). Filterlists are blacklists, not whitelists, so they only grow when well-known entities play foul.