🐡 New in Chrome 115: WebHID in Extension Service Workers and more 🐡

15 views
Skip to first unread message

Ajay Rahatekar

unread,
Jun 21, 2023, 2:05:56 PM6/21/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/ 


M115

__________________________________________________________________________________________

Features Releasing to Stable


WebHID in Extension Service Workers

Contributors:  mattre...@chromium.orgchen...@google.com


Chromestatus     Spec    PSA      Bug 


Allows web developers to use WebHID API when responding to extension events by exposing the WebHID API to Service Workers registered by browser extensions. This API will not yet be exposed to Service Workers registered by sites; the implementation experience gained by supporting the API for extensions will be valuable for such a future project.


As Chrome Apps APIs will soon be deprecated, developers are encouraged to migrate to web apps or Chrome Extensions. For the Chrome Extension case, Manifest V3 deprecates the background page and requires developers to migrate to service workers. As a result, it is required to support WebHID in Extension Service Workers.








Web SQL Deprecation and Removal

Contributors:  ay...@chromium.org


Chromestatus     Spec    I2DR      Bug 


Web SQL is little used, and since Safari removed it in 2019, only Chromium-based browsers have supported it. It requires frequent security fixes, and developers have been discouraged from using it for years. Since 2022, we have been working to remove it.

Now, we have SQLite over Wasm, a superior cross-browser replacement. Our outreach to developers, and our search for Web SQL users on the open web, in Enterprise, in Extensions, and elsewhere is nearly complete. In M115, we're placing a deprecation message in DevTools.


The following is our target timeline for full removal:


  • M101 - 123 - Enterprise Policy

  • M115 - Deprecation message

  • M118-123  - Deprecation trial

  • M119 - API Removal












__________________________________________________________________________________________

Features entering Origin Trial


Storage Buckets API

Contributors:  est...@chromium.org, ay...@chromium.org


Chromestatus     Spec    Bug      Intent to Experiment


Storage Buckets allows sites the ability to create multiple storage buckets to organize their data, allowing user agents to delete each bucket independently of other buckets. Each storage bucket can store data associated with established storage APIs such as IndexedDB and CacheStorage.

Motivation

Currently, when there is storage pressure or the user has a low disk device, sites have no control over how their storage gets evicted during browser storage eviction. Today, there is only a binary choice to either persist or delete all the data stored by a site. Storage Buckets API will allow sites to partition data, manage quota, and set eviction prioritization so sites can specify which bucket to remove first during browser storage eviction.










Compute Pressure API Origin Trial 2

Contributors:  kenneth.r.c...@intel.com, arnaud...@intel.com, wei4...@intel.com 


Chromestatus     Spec    Bug       Intent to Experiment


The Compute Pressure API will give developers a better (and privacy preserving) understanding of the compute load the user’s device is under to take dynamic action. It allows the implementation to use the right underlying hardware metrics to ensure that users can take advantage of all the processing power available to them as long as the system is not under unmanageable stress.


“Pressure” is a generic term by design – at the moment it is calculated based on CPU load, but future plans include using signals from temperature and battery status, for example.











Please reach out with any questions, comments or suggestions.

Ben Morss, Ajay Rahatekar and the Fugu team.

Reply all
Reply to author
Forward
0 new messages