Press "Enter" to skip to content

Google Chrome 158 Stable Rolls Out with XSLT Removal and New Web Install API

Google released version 158 of the Chrome stable channel for desktop computers on November 17, local time. The update, identified as builds 158.0.8127.36 and 158.0.8127.37 for Windows and macOS and 158.0.8127.36 for Linux, is being distributed gradually to existing users. The headline changes focus on the removal of native XSLT support, the remediation of 204 security issues, and the addition of a Web Install API that enables websites to trigger direct installation of web applications.

End of XSLT support across Chrome

XSLT, an XML‑based language used to transform XML documents into other formats such as HTML, has been part of all major browsers since its standardisation in 1999. Chrome has historically relied on the C library libxslt to perform these transformations. Google cited repeated memory‑safety problems in libxslt, including buffer‑overflow vulnerabilities, as the reason for its removal. Although the library’s usage has declined, Google considered it a lingering attack surface.

Starting with Chrome 158, XSLT processing is disabled for the general stable audience. The feature remains available only to sites enrolled in an origin trial or to enterprises that enable the “XSLTEnabled” policy. Both the trial and the policy exception are slated to expire with Chrome 176, after which XSLT will be fully turned off for all users. Developers of web applications that depend on XSLT will need to migrate to alternative approaches, such as JavaScript‑based transformations.

The move aligns Chrome with similar decisions made by Mozilla’s Gecko engine and Apple’s WebKit, which have also signalled intent to deprecate XSLT. Industry observers view this as a broader consolidation around the removal of the technology from mainstream browsers.

Web Install API simplifies web‑app deployment

The most visible new capability in Chrome 158 is the Web Install API. By invoking navigator.install() with the URL of a web app manifest, a site can prompt the browser to install the app directly, without the need for custom UI code that previously relied on events such as beforeinstallprompt. The API also permits installation of apps hosted on different origins, expanding the range of distribution scenarios developers can support.

In addition to the JavaScript method, Chrome introduces an install element that can be placed in HTML to trigger the same behaviour without scripting. Enterprise administrators can control the feature through the “WebAppInstallByUserEnabled” policy and the Permissions Policy entry “web‑app‑installation,” giving organisations the ability to restrict or allow installations according to internal security guidelines.

Developer‑focused enhancements and security patches

Chrome 158 adds a suite of CSS pseudo‑classes that reflect the playback state of media elements. The new selectors—:playing, :paused, :seeking, :buffering, :stalled, :muted and :volume-locked—allow designers to style audio or video elements based on their runtime status without JavaScript. A companion selector, ::highlight(*), provides a generic way to style all custom highlights, complementing the existing per‑name highlight syntax.

Other layout and rendering updates include the introduction of the flow-start and flow-end keywords in CSS layout, and the extension of object-fit and object-position properties to SVG content loaded via object and embed elements. The Web Audio API gains an incremental rendering mode for OfflineAudioContext, which reduces memory consumption when processing large audio buffers.

On the Android side, Chrome now supports the WebHID API, enabling web pages to communicate with Human Interface Devices such as keyboards, mice and game controllers. The feature requires Android 13 (API level 37) or newer. While the desktop version has offered WebHID since Chrome 89, Android WebView remains excluded because it lacks the necessary device‑selection UI and permission handling.

From a security perspective, Chrome 158 incorporates 204 vulnerability fixes. Six of these are classified as Critical, including a use‑after‑free in WebView (CVE‑2026‑130963), an out‑of‑bounds write in the GPU process (CVE‑2026‑131031), a buffer overflow in the Media subsystem (CVE‑2026‑131060), a use‑after‑free in the garbage collector (CVE‑2026‑131008), an out‑of‑bounds write in the ANGLE graphics layer (CVE‑2026‑131054) and a use‑after‑free in WebAudio (CVE‑2026‑130975). Google did not disclose any exploits observed in the wild for this release.

The update also adds a Permissions Policy entry named focus-without-user-activation, which can restrict focus changes that occur without direct user interaction, further tightening the browser’s security posture.

Chrome 158 continues to support Windows 10 or later (with an ARM build requiring Windows 11), macOS Ventura (13) or later, and Linux distributions. The update is delivered automatically to existing installations, though users can also trigger a manual refresh via the Settings page at chrome://settings/help. A restart of the browser is required for the new version to take effect. The next stable release, Chrome 159, is scheduled for December 8, 2026.

For organisations that have built internal tools or document‑conversion pipelines around XSLT, the deprecation timeline—ending with full disablement in Chrome 176—creates a narrow window to transition to alternative technologies. Meanwhile, the Web Install API offers a streamlined path for developers seeking to distribute web‑based applications without relying on native installers, though corporate IT teams will likely need to employ policy controls to prevent unauthorized installations.

Be First to Comment

Leave a Reply

Your email address will not be published. Required fields are marked *