Conflict with HTTPS Everywhere extension in Chrome about ublock

[gorhill]

The last extension installed wins the ability to redirect over others when multiple extensions try to redirect a single net request.

In the current case, it is completely harmless, as the request which HTTP-E would have redirected is a request to block anyways.

But thinking of it, if ever a user installs HTTPS-E after uBlock, there is harm, as HTTPS-E will redirect a request which was intended to be blocked, which means uBlock won't be able to block it.

Looks like uBlock has to block outright without using redirection at all. This means #7 will still show the browser's default placeholder when a resource cannot be fetched, that is until I fix it completely (collapsing the DOM counterpart off a request).