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
Before #55 it was possible to delete a file by just having access to a file handle. I.e. you could get a file handle from showSaveFilePicker, decide you don't want to save after all, and delete the file. Since now deletion requires access to the parent directory this is no longer possible (as pointed out in https://crbug.com/1114923), and I think we might want to bring back a "remove self" method, at least for file handles.
The text was updated successfully, but these errors were encountered:
This is going to be exciting to spec... we'll need to clarify that for files/dirs w/ multiple hardlinks/symlinks, the entry that gets deleted is the entry corresponding to the path that was used to obtain the handle.
Before #55 it was possible to delete a file by just having access to a file handle. I.e. you could get a file handle from showSaveFilePicker, decide you don't want to save after all, and delete the file. Since now deletion requires access to the parent directory this is no longer possible (as pointed out in https://crbug.com/1114923), and I think we might want to bring back a "remove self" method, at least for file handles.
The text was updated successfully, but these errors were encountered: