dylanPowers / ipfs-chrome-extension

Access gateway.ipfs.io urls the way they were meant: from your locally running ipfs daemon
BSD 3-Clause "New" or "Revised" License
68 stars 9 forks source link

Make permissions optional #4

Closed dylanPowers closed 9 years ago

dylanPowers commented 9 years ago

This was thoroughly pursued, but unfortunately Chrome's extension api isn't what it seems when it comes to optional permissions. Optional permissions require user interaction to enable and must be re-enabled upon every browser restart and app upgrade. It's very short sighted on the part of the Chrome developers because that means I can't have you, the user, enable a permission in the options prompt and be merry on our way. In order to use Chrome's optional permissions with this app as it's currently implemented in Chrome, you, the user, would be required to either a) Visit the options prompt for the app every time your browser was opened to re-enable the options, or b) Have a little pop-up on the url bar that you'd have to remember to click to grant permissions. But why? I ask. That's an extra step/button you'd be constantly stuck clicking when you shouldn't have to. What if all your extensions did this? And that is why we can't have nice things.

So alas, sorry tin foil hatters, you're stuck with this extension having access to all urls. DEAL WIT IT!

For when Chrome improves, the relevant work can be found in the branch optional at the git hash 6808eba9f6631786c1283efa615316fca5f0af53 Relevant Chrome issue: https://code.google.com/p/chromium/issues/detail?id=125706