>who would ever expect 'view-source' to have a blacklist or be controllable by the web page i would expect that when a browser displays source code at a url th

>who would ever expect 'view-source' to have a blacklist or be controllable by the web page i would expect that when a browser displays source code at a url that looks like view-source://the-url-of-the-page, and gives me a pattern-matching blacklist feature, then blocking view-source://* would block urls matching that pattern. having a blacklist feature that selectively doesn't work on certain types of URLs seems like a bug to me. removing a special-case exclusion is hardly unintuitive behaviour, unless you're using the definition of "unintuitive" that means "something i don't like"