Connection-Allowlist in Chrome 152 lets websites declare which endpoints a document or worker may connect to. Start with Report-Only, test real workflows, and enable blocking only afterward.
Browsing: Chrome
The CPU Performance API can help websites select an initial interface profile based on CPU performance tiers. Combined with the Compute Pressure API, it can reduce effects and background tasks when the CPU is under load, but a fallback is still necessary because support remains uneven.
Chrome is expected to remove browser-side XSLT in the Chrome 158 rollout. This guide shows how to find dependencies, choose an alternative, and safely test an XML website.
To reduce web notification spam, audit the permission request flow, message content, FCM registrations, and Google’s Abusive Notifications Report. FCM only delivers messages; Chrome is where users grant or revoke permission.
WebMCP lets a website describe selected actions as tools with clear names, descriptions, and parameters for compatible AI agents. This guide focuses on the Declarative API: start with an existing HTML form, test whether it can be called, and keep authentication and authorization in the backend.