> …but the proposed declarativeNetRequest API isn’t a good replacement. So where does that leave us?
Exactly. The issue is Google is using the removal of this "bad API" as an excuse to end ad-blocking in Chrome. If it only wanted to remove the bad API and secure users, it would have announced a better alternative for ad-blockers at the same time.
2 comments
[ 3.3 ms ] story [ 15.1 ms ] threadExactly. The issue is Google is using the removal of this "bad API" as an excuse to end ad-blocking in Chrome. If it only wanted to remove the bad API and secure users, it would have announced a better alternative for ad-blockers at the same time.