Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The browser is the sandbox

aifoc.us

Post reply on HN
Print view View original

11–20 of 202 posts

Re: The browser is the sandbox

#13

Post by vbezhenar »

modeless wrote: post #9

Last I looked (a couple of years ago), you could ask the user for read-write access to a directory in Chrome using the File System Access API, however you couldn't persist this access, so the user would have to manually re-grant permission every time you reloaded the tab. Has this been fixed yet? It's a showstopper for the most interesting uses of the File System Access API IMO.

Yes, it was improved.

https://developer.chrome.com/blog/persistent-permissions-for...

Re: The browser is the sandbox

#15

Post by nezhar »

modeless wrote: post #9

Last I looked (a couple of years ago), you could ask the user for read-write access to a directory in Chrome using the File System Access API, however you couldn't persist this access, so the user would have to manually re-grant permission every time you reloaded the tab. Has this been fixed yet? It's a showstopper for the most interesting uses of the File System Access API IMO.

Good question! Since this is an extension of input, I'm not sure if this is defined: https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputEl....

On my desktop Chrome on Ubuntu, it seems to be persistent, but on my Android phone in Chrome, it loses the directory if I refresh.

Re: The browser is the sandbox

#17

Post by drysine »

stevefan1999 wrote: post #4

We never say that it isn't. There is a reason Google developed NaCl in the first place that inspired WebAssembly to become the ultimate sandbox standard. Not only that, DOM, JS and CSS also serves as a sandbox of rendering standard, and the capability based design is also seen throughout many browsers even starting with the Netscape Navigator. Locking down features to have a unified experience is what a browser shoul…

>all of them being a horrible one

Silverlight was nice, pity it got discontinued.

Re: The browser is the sandbox

#18

Post by ijustlovemath »

I've found it interesting that systemd and Linux user permissions/groups never come into the sandboxing discussions. They're both quite robust, offer a good deal of customization in concert,and by their nature, are fairly low cost.

Re: The browser is the sandbox

#19

Post by modeless »

vbezhenar wrote: post #13
modeless wrote: post #9

Last I looked (a couple of years ago), you could ask the user for read-write access to a directory in Chrome using the File System Access API, however you couldn't persist this access, so the user would have to manually re-grant permission every time you reloaded the tab. Has this been fixed yet? It's a showstopper for the most interesting uses of the File System Access API IMO.

Yes, it was improved. https://developer.chrome.com/blog/persistent-permissions-for...

Thanks, this looks like a very sensible behavior.

Re: The browser is the sandbox

#20

Post by utopiah »

Wrong title, if it's "File System Access API (still Chrome-only as far as I can tell)" then it should read "A browser is the sandbox".

At the risk of sounding obvious :

- Chrome (and Chromium) is a product made and driven by one of the largest advertising company (Alphabet, formally Google) as a strategical tool for its business model

- Chrome is one browser among many, it is not a de facto "standard" just because it is very popular. The fact that there are a LOT of people unable to use it (iOS users) even if they wanted to proves the point.

It's quite important not to amalgamate some experimental features put in place by some vendors (yes, even the most popular ones) as "the browser".

Post reply on HN