-
Notifications
You must be signed in to change notification settings - Fork 23
Origin Private File System – identification of buckets (similarly to FAS API showSaveFilePicker) #155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
From your response on the other issue:
For starters, the spec doesn't mention "OPFS" because there may be more than one file system per origin. See #92 The question of whether or not you'll get the same file system instance in SESS_ONE and SESS_TWO has the same answer as whether or not you'll get the same IndexedDB instance. Which is a hint that you're looking in the wrong spec :) The FS spec specifies the algorithm for |
Can't you inspect the data in the OPFS (say, using https://github.com/tomayac/opfs-explorer/) at the start of SESS_TWO to check whether it contains any data? |
Yes, technically I can perform a use-case and see the behaviour deductively. |
What is the issue with the File System Standard?
As titled.
This is also related to my detailed question on issue:web-platform-tests/interop#172 (comment)
Perhaps I am from those very few web developers that read specifications, but just to clarify: Does the specification describes means for identification of bucket(s) per origin ?
Cheers ♥
The text was updated successfully, but these errors were encountered: