🐡 New in Chrome 121: Multiple Readers and Writers in File System Access API and more 🐡

21 views

Skip to first unread message

Ajay Rahatekar

unread,

Dec 27, 2023, 3:28:39 PM12/27/23

to fugu...@chromium.org

Welcome to the latest edition of the regular Fugu + PWA update. Here, you'll find all the latest news about our work on the Fugu APIs, plus a sampling of recent work with partners.

As always, our project tracker is available at fugu-tracker.web.app/

Notes:

There was no newsletter for M120, since no Fugu features were released in that milestone.

M121

__________________________________________________________________________________________

Features Releasing to Stable

Multiple Readers and Writers in File System Access API

Contributors: mem...@google.com ds...@google.com

Chromestatus Spec Intent to Ship Bug

Currently, only one FileSystemSyncAccessHandle may be open at a time per file, preventing an origin from reading and writing to the same file from multiple tabs easily. Conversely, multiple FileSystemWritableFileStreams can be simultaneously open, letting multiple writers clobber each other. Introducing new locking modes for FileSystemSyncAccessHandle and FileSystemWritableFileStream allows opening either multiple readers/writers or an exclusive writer to a file entry, depending on the application's use case.

Link Capturing on Windows, MacOS and Linux

Contributors: diby...@google.com pjmcl...@google.com dmu...@google.com

Bug

This feature provides a seamless transition for opening a link inside an installed PWA from other app surfaces in chrome (like tabs in the browser or links on search results).

In M121, the feature is shipping to 1% Stable as an experiment to collect data to determine the default behavior for the feature.

The feature is expected to ship to all users on Stable in Chrome M122/123. Link Capturing is already available on ChromeOS.

__________________________________________________________________________________________

Features Releasing to Origin Trial

Web App Scope Extensions

Contributors: lu...@microsoft.com luig...@microsoft.com alanc...@chromium.org

Chromestatus Intent to Experiment Bug

Web app scope (defined by the scope field) can only be defined with a path from a single origin. It is used to determine whether an app window's current document is a part of the app. It also determines what URLs are allowable in other manifest members.

With a mechanism like "scope_extensions", developers are able to expand the behaviors of their app to include other origins if there is agreement between the primary origin of a web app and the associated origins.