You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I couldn’t find any information on what permissions newly created files should have (note, I'm talking about Unix-like permissions, like rw-r--r--, not browser permissions).
On my computer (running Mac OS Catalina), it looks like creating new files gives them permission rw------- instead of the expected rw-r--r--. Is that intended? It is a bit problematic for my use case as I am creating files that are meant to be read back by a local web server, and the web server fails reading such files (it is presumably running as its own user). Writing over existing files does keep the existing rw-r--r-- permission, it’s only creating new files that is problematic.
Not sure if it is a spec or a browser issue, but I think the spec should at least say something about that.
I couldn’t find any information on what permissions newly created files should have (note, I'm talking about Unix-like permissions, like
rw-r--r--
, not browser permissions).On my computer (running Mac OS Catalina), it looks like creating new files gives them permission
rw-------
instead of the expectedrw-r--r--
. Is that intended? It is a bit problematic for my use case as I am creating files that are meant to be read back by a local web server, and the web server fails reading such files (it is presumably running as its own user). Writing over existing files does keep the existingrw-r--r--
permission, it’s only creating new files that is problematic.Not sure if it is a spec or a browser issue, but I think the spec should at least say something about that.
You can easily reproduce it with the Text Editor example: https://googlechromelabs.github.io/text-editor/
The text was updated successfully, but these errors were encountered: