Difference between revisions of "Origin Private File System"
(→Full Title or Meme) |
(→Context) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
==Full Title or Meme== | ==Full Title or Meme== | ||
File systems that are only available to web sites from a common origin as that is defined, is called an [[Origin Private File System]] (OPFS). | File systems that are only available to web sites from a common origin as that is defined, is called an [[Origin Private File System]] (OPFS). | ||
+ | |||
+ | ==Context== | ||
+ | A part of [[Origin Access Control]] dealing with the File System on a [[Smartphone]] operating system. | ||
==Solutions== | ==Solutions== | ||
Line 7: | Line 10: | ||
Contact emails | Contact emails | ||
'Daseul Lee' | 'Daseul Lee' | ||
− | Sep 21, 2022, 12:10 PM | + | Sep 21, 2022, 12:10 PM dslee@google.com |
− | dslee@google.com | ||
− | |||
Specification | Specification | ||
https://wicg.github.io/file-system-access/#sandboxed-filesystem | https://wicg.github.io/file-system-access/#sandboxed-filesystem | ||
− | |||
Design docs | Design docs | ||
https://web.dev/file-system-access/#accessing-the-origin-private-file-system | https://web.dev/file-system-access/#accessing-the-origin-private-file-system | ||
+ | Summary = Enable the Origin Private File System (OPFS) part of File System Access API on Android. This includes all of the File System Access (FSA) API surface, minus show*Picker() methods and Drag-and-Drop API integration. | ||
− | + | With FSA API on OPFS, a site can access its per-origin, private file system and are able to perform file operations via `FileSystemSyncAccessHandle` with improved performance. The original API, including both OPFS and non-OPFS, was shipped in M86 for desktop, and the extension with SyncAccessHandle was shipped in M102. | |
− | + | * https://chromestatus.com/feature/6284708426022912 | |
− | + | * https://chromestatus.com/feature/5702777582911488 | |
− | |||
− | With FSA API on OPFS, a site can access its per-origin, private file system and are able to perform file operations via `FileSystemSyncAccessHandle` with improved performance. | ||
− | |||
− | |||
− | The original API, including both OPFS and non-OPFS, was shipped in M86 for desktop, and the extension with SyncAccessHandle was shipped in M102. | ||
− | |||
− | https://chromestatus.com/feature/6284708426022912 | ||
− | |||
− | https://chromestatus.com/feature/5702777582911488 | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
+ | TAG review = This API has been shipped on Windows, Mac, Linux and Chrome OS, with two parts. The API to be shipped on Android is the same, thus relying on the previously completed TAG reviews: | ||
* File System Access API: https://github.com/w3ctag/design-reviews/issues/390 | * File System Access API: https://github.com/w3ctag/design-reviews/issues/390 | ||
− | |||
* Access Handle: https://github.com/w3ctag/design-reviews/issues/664 | * Access Handle: https://github.com/w3ctag/design-reviews/issues/664 | ||
Line 55: | Line 34: | ||
Risks | Risks | ||
+ | * Interoperability and Compatibility | ||
+ | ** Gecko: In development (https://bugzilla.mozilla.org/show_bug.cgi?id=1748667) | ||
+ | ** WebKit: In development (https://bugs.webkit.org/show_bug.cgi?id=231706) | ||
+ | ** Web developers: Strongly positive (https://crbug.com/1011535) | ||
− | + | Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? = | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? | ||
− | |||
No, it does not change any existing APIs but to enable a new one. | No, it does not change any existing APIs but to enable a new one. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? | Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? | ||
Line 89: | Line 47: | ||
This feature was initially launched on desktop, and this proposal includes Android Chrome and Android WebView. | This feature was initially launched on desktop, and this proposal includes Android Chrome and Android WebView. | ||
− | + | Flag name: FileSystemAccessOriginPrivate | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | Flag name | ||
− | FileSystemAccessOriginPrivate | ||
− | |||
− | |||
− | |||
− | |||
− | |||
Tracking bug | Tracking bug | ||
https://bugs.chromium.org/p/chromium/issues/detail?id=1354273 | https://bugs.chromium.org/p/chromium/issues/detail?id=1354273 | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Anticipated spec changes | Anticipated spec changes | ||
No spec changes. This API has shipped on other platforms, and the proposal is to enable the existing API on Android. | No spec changes. This API has shipped on other platforms, and the proposal is to enable the existing API on Android. | ||
− | |||
− | |||
Link to entry on the Chrome Platform Status | Link to entry on the Chrome Platform Status | ||
https://chromestatus.com/feature/5079634203377664 | https://chromestatus.com/feature/5079634203377664 | ||
− | |||
− | |||
− | |||
− | |||
-- | -- | ||
− | |||
− | |||
− | |||
− | |||
− | |||
LGTM1 To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfVRNiZN7KnJEmPsdtq4kJzZZ%3DKSdUUjLSEAm7e92U30Cg% | LGTM1 To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfVRNiZN7KnJEmPsdtq4kJzZZ%3DKSdUUjLSEAm7e92U30Cg% | ||
− | + | 'Daseul Lee' via blink-dev | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Thanks for the review! WPT is no longer available to run on Android. It looks like there is some coverage for Drag-and-Drop, but as Marijn mentioned, it doesn't | Thanks for the review! WPT is no longer available to run on Android. It looks like there is some coverage for Drag-and-Drop, but as Marijn mentioned, it doesn't | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ded412c8-0757-4446-b364-0b7d52a25a90n%40chromium.org. | To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ded412c8-0757-4446-b364-0b7d52a25a90n%40chromium.org. | ||
Latest revision as of 12:15, 10 February 2023
Contents
Full Title or Meme
File systems that are only available to web sites from a common origin as that is defined, is called an Origin Private File System (OPFS).
Context
A part of Origin Access Control dealing with the File System on a Smartphone operating system.
Solutions
Origin Private File System (OPFS) on Android
Contact emails 'Daseul Lee' Sep 21, 2022, 12:10 PM dslee@google.com
Specification https://wicg.github.io/file-system-access/#sandboxed-filesystem
Design docs https://web.dev/file-system-access/#accessing-the-origin-private-file-system
Summary = Enable the Origin Private File System (OPFS) part of File System Access API on Android. This includes all of the File System Access (FSA) API surface, minus show*Picker() methods and Drag-and-Drop API integration.
With FSA API on OPFS, a site can access its per-origin, private file system and are able to perform file operations via `FileSystemSyncAccessHandle` with improved performance. The original API, including both OPFS and non-OPFS, was shipped in M86 for desktop, and the extension with SyncAccessHandle was shipped in M102.
TAG review = This API has been shipped on Windows, Mac, Linux and Chrome OS, with two parts. The API to be shipped on Android is the same, thus relying on the previously completed TAG reviews:
- File System Access API: https://github.com/w3ctag/design-reviews/issues/390
- Access Handle: https://github.com/w3ctag/design-reviews/issues/664
TAG review status
Completed
Risks
- Interoperability and Compatibility
- Gecko: In development (https://bugzilla.mozilla.org/show_bug.cgi?id=1748667)
- WebKit: In development (https://bugs.webkit.org/show_bug.cgi?id=231706)
- Web developers: Strongly positive (https://crbug.com/1011535)
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? = No, it does not change any existing APIs but to enable a new one.
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? Yes
This feature was initially launched on desktop, and this proposal includes Android Chrome and Android WebView.
Flag name: FileSystemAccessOriginPrivate
Tracking bug https://bugs.chromium.org/p/chromium/issues/detail?id=1354273
Anticipated spec changes No spec changes. This API has shipped on other platforms, and the proposal is to enable the existing API on Android.
Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5079634203377664
--
LGTM1 To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfVRNiZN7KnJEmPsdtq4kJzZZ%3DKSdUUjLSEAm7e92U30Cg%
'Daseul Lee' via blink-dev
Thanks for the review! WPT is no longer available to run on Android. It looks like there is some coverage for Drag-and-Drop, but as Marijn mentioned, it doesn't
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ded412c8-0757-4446-b364-0b7d52a25a90n%40chromium.org.