Chrome 158 Arrives With Faster Releases and the End of XSLT
Chrome 158 reached stable on November 17, and it kills XSLT for good. It is also the first version on Google's new two-week release cycle.

Chrome Now Ships Every Two Weeks
Chrome 158 reached full stable on November 17, and the version number matters less than the schedule behind it. Google moved Chrome to a two-week release cycle starting with Chrome 153 on September 8, down from the four-week cycle the browser used for years. Beta and stable versions now ship every two weeks on desktop, Android, and iOS, while Extended Stable stays on an eight-week cycle. Chrome 158 is the first version most users will notice under the new rhythm, and the practical effect is simple: security fixes and small features arrive faster, and the gap between a fix existing and a fix reaching your browser shrinks.
The headline change in 158 is the removal of XSLT. Starting with this version, Chrome drops support for XSLT, the XML transformation language, for everyone outside the origin trial and enterprise policy. Google cites the security risk of the aging library behind it, and the usage numbers back the decision: only about 0.02% of page loads use XSLT. That is a tiny share of the web, but it is not zero, and the sites that still rely on it are mostly old government portals, enterprise intranets, and legacy publishing systems that have not been touched in years.
What the End of XSLT Means in Practice
For almost everyone reading this, the XSLT removal changes nothing. If you have never heard of XSLT, you do not use it, and your browsing will not notice its absence. The removal matters to a specific group: organizations running internal tools that transform XML documents in the browser, and the developers maintaining them. Those teams need a plan, because the page that rendered fine in Chrome 157 will show raw XML or an error in Chrome 158.
The alternatives are not complicated, just work someone has to do. Move the transformation to the server, where XSLT still runs fine in every language, or rewrite the transform in JavaScript. Google gave this a long runway: the removal was announced well in advance, and enterprise policy can extend support for managed fleets. But long runways only help if someone is watching the runway, and legacy systems are famous for having nobody watching.
The two-week cycle is the change with wider consequences. Faster releases mean faster security patches, which is good news for everyone. It also means web developers and extension authors have less time between a change landing and users receiving it. Extension developers felt this already: Chrome 157 reached full stable on November 3 with four changes affecting existing extensions, and Chrome 158 started its early-stable rollout the next day. The pace is the point. Google is betting that smaller, more frequent updates are safer than big monthly drops, and the early evidence from the 153 to 157 cycle suggests the machinery holds up.
The Browser Race Around Chrome 158
Chrome is not the only browser shipping in November. Firefox 159, released October 27, added scroll-driven animations, which let developers build reading progress bars and reveal-on-scroll effects in plain CSS, without a JavaScript scroll listener or an animation library. Firefox 161 entered public beta testing ahead of a November 24 release, headlined by a customizable keyboard shortcut for copying the current tab's URL and better WebRTC video call quality. Safari 27.0 arrived in September with 844 resolved issues, and WebKit introduced Adaptive Dark Mode in the Safari 27.3 beta on November 3.
The interesting pattern is that the three engines are converging on the same web platform features while competing on release speed and defaults. Scroll-driven animations now work in all three engines. JPEG XL image support landed in Chromium 155 and Firefox 158, though fewer than 0.1% of websites serve JPEG XL so far. The web platform is becoming more uniform, which is good for developers, while the browsers differentiate on update speed, privacy defaults, and AI features.
Chrome's own AI push continues alongside the release train. Google has built AI Mode and Gemini into Chrome and recently added two more AI buttons beneath the search box on the New Tab page. If you find those buttons annoying, you can turn them off with the NTP Starter Chip flag at chrome://flags, though flags are temporary by design and Google has already removed the earlier flag that hid the AI Mode button. The AI buttons are the visible face of Chrome's strategy. The two-week cycle is the engine underneath it.
For most users, the advice is simple: let Chrome update, and check any old internal tools that might use XSLT before the next team meeting. If you want the full picture of what else changed in browsers this month, our Chrome new features overview covers the vertical tabs and Gemini media additions, and our Windows 11 November Patch Tuesday article covers the month's biggest security fixes. The browser is the app most people use most, and in November it got faster, quieter, and a little less backwards compatible, which is exactly the trade the modern web keeps making.


