re spec:
Working on a specification right now and will update this thread once it is
available as a pull request somewhere. For now, I only have the explainer
to offer.
We are currently in discussion with privacy folks and will likely also need
to add a permission prompt "Share that foo.txt is synced via GoogleDrive
with bar.com" to the API.

re test infrastructure:
The API would call into ash-Chrome via ChromeContentBrowserClient
<https://chromium-review.googlesource.com/c/chromium/src/+/4055714/31/chrome/browser/chrome_content_browser_client.cc>
and
crosapi. IIUC the WPT tests would use WebTestContentBrowserClient
<https://source.chromium.org/chromium/chromium/src/+/refs/heads/main:content/web_test/browser/web_test_content_browser_client.h;drc=5578b78366de32caf83044e5ea2268e6d91af766;bpv=1;bpt=1;l=42?gsn=WebTestContentBrowserClient&gs=KYTHE%3A%2F%2FKvYCCrgBa3l0aGU6Ly9jaHJvbWl1bS5nb29nbGVzb3VyY2UuY29tL2NvZGVzZWFyY2gvY2hyb21pdW0vc3JjLy9tYWluP2xhbmc9YyUyQiUyQj9wYXRoPWNvbnRlbnQvd2ViX3Rlc3QvYnJvd3Nlci93ZWJfdGVzdF9jb250ZW50X2Jyb3dzZXJfY2xpZW50LmgjMW85YmgzMXZqbGpQQU4zaGU1aXZ6SUt2Y2tILXhSUUJhT0FpVG9VcE5ESQq4AWt5dGhlOi8vY2hyb21pdW0uZ29vZ2xlc291cmNlLmNvbS9jb2Rlc2VhcmNoL2Nocm9taXVtL3NyYy8vbWFpbj9sYW5nPWMlMkIlMkI_cGF0aD1jb250ZW50L3dlYl90ZXN0L2Jyb3dzZXIvd2ViX3Rlc3RfY29udGVudF9icm93c2VyX2NsaWVudC5oIzhwa0liVjFhRFh2dERJVVdLU1hSRWhxM2hsbUMxTDM5VGdXc2M3SjkxM1U%3D>,
right? So the idea would be to set up fake responses via that controller to
allow WPT tests? If that pattern is okay, then we could indeed write WPT
tests.

Thanks,
Alex


Alexander Hendrich | Software Engineer | hendr...@google.com | Chrome OS
Enterprise


On Mon, Jun 26, 2023 at 8:56 AM Yoav Weiss <yoavwe...@chromium.org> wrote:

>
>
> On Fri, Jun 23, 2023 at 3:28 PM 'Alexander Hendrich' via blink-dev <
> blink-dev@chromium.org> wrote:
>
>> Hello blink-dev team,
>> For now, we are looking to prototype (and later launch) the new web API (
>> FileSystemHandle.getCloudIdentifiers()
>> <https://chromestatus.com/feature/5130687725699072>) for ChromeOS only
>> (with GoogleDrive and OneDrive as providers). Other platforms and providers
>> will come later, but are not prioritized yet. The first CL
>> <https://crrev.com/c/4055714> just started the review process.
>> PTAL, thanks!
>>
>> Contact emailshendr...@chromium.org / hendr...@google.com
>> Mentor: asu...@chromium.org
>>
>> Explainer
>> https://github.com/WICG/file-system-access/blob/main/proposals/CloudIdentifier.md
>>
>> SpecificationNone
>>
>
> Are there plans to specify this?
>
>
>>
>>
>> Summary
>>
>> This proposal adds a new getCloudHandles() method to FileSystemHandle,
>> which allows retrieval of cloud handles for a file/directory. A cloud
>> handle consists of a vendor identifier (e.g. "drive.google.com") and a
>> file identifier. With these, the web app can talk to the cloud storage
>> provider through its APIs directly to retrieve/modify the file. This is
>> useful for web apps to figure out if a file is already backed by cloud
>> storage and allows for easier transfer across machines as just the
>> identifier instead of the entire file contents needing to be transfered.
>>
>>
>> Blink componentBlink>Storage>FileSystem
>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EStorage%3EFileSystem>
>>
>> Motivation
>>
>> Web apps interacting with files/directories via file system access web
>> API can benefit from additional capabilities when they know whether a
>> file/directory is synced via cloud storage and what ID the cloud storage
>> provider is using for it. Use cases: * Remote file handling: If the file
>> should be transferred to another machine, instead of uploading it from the
>> device itself and syncing it back, we can simply pass the cloud identifier
>> for the file/directory to the remote machine, which directly pulls it from
>> the cloud storage provider and also syncs it back. * De-duplication for
>> online document editors: For cloud-based online document editors (Google
>> Docs or Microsoft Office 365 web), the document needs to be in cloud
>> storage (Google Drive or Microsoft OneDrive) before it can be edited. With
>> this API, the web app could detect that a given file is already in cloud
>> storage and edit it directly instead of creating a new duplicate. * Drag &
>> drop into Mail: When sharing a large file via mail, instead of actually
>> transferring the file with the mail as attachment, the web-based mail
>> clients could instead detect that the file is in cloud storage, request it
>> to be shared via link and simply include the link in the mail.
>>
>>
>> Initial public proposal
>> https://github.com/WICG/file-system-access/blob/main/proposals/CloudIdentifier.md
>>
>> TAG review
>> TAG review statusPending
>>
>> Risks
>>
>>
>> Interoperability and Compatibility
>>
>>
>>
>> *Gecko*: No signal
>>
>> *WebKit*: No signal
>>
>> *Web developers*: No signals
>>
>> *Other signals*:
>>
>> WebView application risks
>>
>> Does this intent deprecate or change behavior of existing APIs, such that
>> it has potentially high risk for Android WebView-based applications?
>>
>> No
>>
>>
>>
>> Debuggability
>>
>>
>>
>> Is this feature fully tested by web-platform-tests
>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
>> ?No. Testing this feature requires a cloud storage sync client (e.g.
>> GoogleDrive / OneDrive), which is not possible to mock for WPT tests. The
>> only test we can produce is test that the result for a local file is an
>> empty list.
>>
>
> Can testing infrastructure be added to support WPTs here?
>
>
>>
>>
>> Flag nameFileSystemAccessGetCloudIdentifiers (CL
>> <https://crrev.com/c/4055714> just started review)
>>
>> Requires code in //chrome?True
>>
>> Tracking bughttps://crbug.com/1443354
>>
>> Launch bughttps://launch.corp.google.com/launch/4234443/approver/14472
>>
>> Estimated milestones
>>
>> No milestones specified
>>
>>
>> Link to entry on the Chrome Platform Status
>> https://chromestatus.com/feature/5130687725699072
>>
>> Links to previous Intent discussions
>> This intent message was generated by Chrome Platform Status
>> <https://chromestatus.com/>.
>>
>> Thank you,
>> Alexander Hendrich
>> Alexander Hendrich | Software Engineer | hendr...@google.com | Chrome OS
>> Enterprise
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "blink-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to blink-dev+unsubscr...@chromium.org.
>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALjDZRCx37hwFjsJ5z5OYz0TMr9gpD_3Tk8CasG_QbSVk2Zr0w%40mail.gmail.com
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALjDZRCx37hwFjsJ5z5OYz0TMr9gpD_3Tk8CasG_QbSVk2Zr0w%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALjDZRAM5tpCaaNwaYkFoWBHnr6DrYP3m3qM35ksRXALQm85jw%40mail.gmail.com.

Reply via email to