Hacker News new | ask | show | jobs
by byuu 3529 days ago
> By definition, browser extensions need to be able to access things such as page content. What would stop someone from writing a extension that captures your bank credentials? Nothing.

Completely agreed. This is why it's so frustrating that all of the browser vendors have moved to this, "gut every minor option/feature possible, people can just get an extension" attitude.

For Firefox:

* removing the option to not maintain download history

* removing the option for the compact drop-down menu from the URL bar

* forcing tabs on top

* forcing refresh button to the right-hand side of the interface

For Chrome:

* removing backspace navigation (you may dislike it, but others don't)

* disabling middle-click to scroll on Linux

* removing the option to set your new tab page (eg to about:blank)

* not letting you prevent HTML5 video autoplay

* not letting you disable WebRTC

Just the backspace extension alone requires basically carte blanche access to everything just to be able to insert a tiny Javascript function to catch the keypress.

I'm not asking for us to go back to the Mozilla suite with integrated mail client, news reader, etc. Just ... it's okay to have an "advanced options" section that lets us control some of this really simple, really basic stuff. And not only okay, a major security benefit to do so. All the focus on web security, you'd think they'd take this stuff more seriously.

1 comments

Or more fine grained permissions.

They could at least make it possible choosing not to upgrade a very simple extension which we may have been personally reviewed.

I want a fixed (read: no updates) extension that does this: On key press, check if the key is backspace, when it is, check if any form element is focused, when not, go back. One line of JS, I guess three with nice formatting. If I create this, I need to submit it to the Chrome Store so Chrome won't complain about untrusted extensions.

Of course they also removed the ability to tell it that I know what I'm doing.

I agree but unfortunately it's not a very popular design pattern these days.

Because of this I basically have no applications installed on my android smartphone since even trivial applications often end up requiring ridiculous amounts of privileges (often for relatively minor features) and of course there's no way to fine tune what you allow and what you don't.

Honestly I think that's a terrible habit to give your users, just ignore the privilege list since there's nothing you can do about it and click "sure whatever".

Devs should have to justify why the app needs the feature and I should be able to disable it if it's not critical for the application to work correctly. It would make it a bit harder to write and test those apps but it's not like it's rocket science either...

Sidenote: It is pretty much exactly the Googles (alas, auto-updated) "Go Back With Backspace" [0] does: [1] (you forgot the shift backspace, Google as well in past versions).

[0] https://chrome.google.com/webstore/detail/go-back-with-backs...

[1] https://crx.dam.io/source/crxviewer.html?crx=https://crx.dam... (nice to walk trough history of this file though versions https://crx.dam.io/ext/eekailopagacbcdloonjhbiecobagjci.html )