My issues with Chrome's handling of extensions

June 9, 2011

This got long enough that I've pulled it out of the original entry into a standalone entry.

On an ongoing basis, two issues with Chrome extensions especially grate on me. The first is that Chrome extensions are disabled when you're visiting Google's website(s). This has a vaguely sensible excuse for security reasons (Google's website hosts the Chrome extensions), but the side effects are unpleasant since extensions provide significant portions of the browser interface for me (in the form of mouse gestures and middle mouse autoscrolling), plus I am not happy about losing the ability to block all JavaScript.

(No, I don't have Google whitelisted for NoScript in Firefox. Yes, I'm peculiar.)

The second is that NotScripts does not have anywhere near as good an interface as NoScript does. I'm not sure if this is a Chrome limitation or just that NotScripts has not gone the extra distance, but it sort of feels like a Chrome issue to me; given their other behavior with extensions, I find it all too easy to believe that Chrome has deliberately limited what GUI interfaces are available to extensions and forced NotScript to jump through hoops to get even as much as it does now. When I'm using NotScripts, it's less clear what the state of things is on the current page, it's harder and takes me longer to do things, and I feel that the interface is not as clear.

(For example, NoScript lets you deal with multiple JavaScript sources in one trip through its menu. On NotScripts, you can only modify one source at a time; if you have multiple sources, you get to click over and over on the menu. Another example is that I have a NoScript button for 'temporarily enable this site' right by the URL bar, which makes it very convenient; a lot of the time I click the button and I'm done. There is no equivalent I know of in NotScript.)

Written on 09 June 2011.
« More impressions of Google Chrome
What __slots__ are good for (or, how to use slots to save memory) »

Page tools: View Source, Add Comment.
Login: Password:
Atom Syndication: Recent Comments.

Last modified: Thu Jun 9 02:16:35 2011
This dinky wiki is brought to you by the Insane Hackers Guild, Python sub-branch.