🐡 New in Chrome 130: Windows System Location Permission Integration, Web Serial connected attribute and more 🐡

[Ajay Rahatekar]

Fugu & PWA Update for Chrome 130

Our previous newsletters

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.

M130

Features Releasing to Stable

System Media Controls per PWA

liahi...@microsoft.com

Bug 

This feature introduces support for System Media Controls to be instanced for each dPWA that’s playing audio.

This feature previously shipped in Chrome on Windows in M124. In M130 the feature is shipping on MacOS. This feature is owned by the Microsoft team and Google helped with approvals for shipping in Chrome.

Windows system location permission integration

mattre...@chromium.org

In response to Microsoft's planned changes in Windows 11 24H2, which will restrict access to Wi-Fi and location APIs when location privacy is disabled, Chrome's implementation of the W3C Geolocation API will need to adapt. Similar to its behavior on macOS, Chrome on Windows will integrate with the system-level location preference, prompting users to enable access if it's currently off. This ensures methods that retrieve information about nearby Wi-Fi networks continue to function as expected

• This change is rolling out gradually based on feedback from users and developers on location accuracy changes.

• Users will need to grant permission through Windows settings and might see their location in mapping apps change because of the new data source.

• This change will enable users to use their device’s built-in GPS in web-based mapping applications.

Web Serial connected attribute and RFCOMM connection events

mattre...@google.com

Chromestatus      Bug      Launch bug      Blog

This feature adds a boolean SerialPort.connected attribute. The attribute is true if the serial port is logically connected. For wired serial ports, a port is logically connected if the port is physically attached to the system. For wireless serial ports, a port is logically connected if the device hosting the port has any open connections to the host.

Previously, only wired serial ports dispatched connect and disconnect events. With this feature, Bluetooth RFCOMM serial ports will dispatch these events when the port becomes logically connected or disconnected.

This feature is intended to allow applications to detect when a Bluetooth RFCOMM serial port is available without opening the port.

Please reach out with any questions, comments or suggestions.

Ajay Rahatekar and the Fugu team.