Did anyone else notice the double meaning of the term "blocking"? This bit tipped me off to the confusion: > And he argues that if the blocking nature of the w

Did anyone else notice the double meaning of the term "blocking"? This bit tipped me off to the confusion: > And he argues that if the blocking nature of the webRequest API really represents a performance concern, Google could just adopt Firefox's approach which uses a technique called Promises to return a non-blocking/asynchronous response. They do explicitly say "content blocking" in a few places, but in most instances they say "blocking webRequest API" which might actually refer to blocking-as-opposed-to-non-blocking and not ad-blocking.