3 ms·

Google developer Peter Kasting's comment on this is here: http://hackademix.net/2009/12/10/why-chrome-has-no-noscript/#comment-17007 http://hackademix.net/2009

Google developer Peter Kasting's comment on this is here: http://hackademix.net/2009/12/10/why-chrome-has-no-noscript/#comment-17007 http://hackademix.net/2009/12/10/why-chrome-has-no-noscript/... That comment points to a Chromium tracking bug, here: http://code.google.com/p/chromium/issues/detail?id=16932 http://code.google.com/p/chromium/issues/detail?id=16932 It looks like while a developer at Google was working on this project, that developer left Google in October and there's been no replacement. While this doesn't suggest the feature is the highest priority for Google, it also doesn't suggest Google is deliberately intending to prevent JavaScript or advertising blocking. Sometimes things that didn't get done just didn't get done.

pavs 17y ago
To be fair, if they wanted to be hostile towards ads blocking extensions in general they would have made it really hard or impossible to develop them in the first place; or wouldn't even allow them to be hosted on Google extensions website. To my last count they currently have 5 ad blocking extensions on Google extensions gallery. One of the is the second most downloaded Chrome Extension. Generally speaking Google has done so much with Chrome browser in such a short time, I don't mind giving them the benefit of doubt that they didn't get around fixing or implementing the said bug/feature.