Google’s Chrome 158 is now the stable version of the browser. The release adds new ways for sites to offer app installation, new CSS selectors for media elements and expanded hardware access on Android. It also turns off a legacy feature by default and includes 204 security fixes.
Web Install API
Sites can now call navigator.install() with a manifest URL to ask the user to install a web app. An install element provides the same capability without JavaScript. Organizations can restrict the feature with the WebAppInstallByUserEnabled policy or through the web-app-installation Permissions Policy.
Media state pseudo-classes
Chrome 158 supports seven CSS pseudo-classes that reflect the state of audio and video elements: :playing, :paused, :seeking, :buffering, :stalled, :muted and :volume-locked. Developers can style custom media controls with CSS alone, for example showing a spinner only while a video is buffering.
WebHID on Android
The WebHID API, which lets web apps talk to devices such as game controllers and specialized keyboards, now works in Chrome for Android on Android 17 (API level 37) or later. Android WebView is not included.
Smaller additions
The release adds ::highlight(*) for styling all custom highlights at once and a side attribute for SVG textPath.
XSLT disabled by default
XSLT, a technology for transforming XML documents in the browser, is now disabled by default. Sites that still depend on it can use an origin trial for now, and enterprises can re-enable it with the XSLTEnabled policy. If your site renders XML feeds with an XSLT stylesheet, test it now and plan a server-side or JavaScript replacement.
Update now
With 204 security fixes, updating is worthwhile even if you do not need the new features. Chrome usually updates itself; you can trigger it from Settings, then About Chrome. Chrome 159 is scheduled for December 8, 2026.
Sources:




