A Release Defined by Developer Priorities
Apple has released Safari 26.4, and by any measure it is one of the most substantive WebKit updates in recent memory. The release ships with 44 new features, 191 bug fixes, and a single deprecation — the FontFaceSet constructor from the CSS Font Loading API — making it unusually dense with changes that web developers have long requested.
What makes this cycle stand out is where the priorities came from. Apple's Web Developer Experience evangelist Jen Simmons said the team shifted its focus based directly on developer surveys conducted throughout 2025. Rather than chasing new headline features, engineers spent significant effort closing gaps with other browsers and fixing longstanding specification inconsistencies that had made cross-platform web development frustrating for years.
Three Headline Additions
Among the 44 new features, three are likely to have the broadest practical impact on the web.
CSS Grid Lanes delivers a layout capability that designers and front-end developers have requested for years. Grid Lanes allow richer visual gallery and masonry-style layouts that were previously only possible through JavaScript hacks or CSS workarounds. Now they can be expressed directly in stylesheet rules, reducing complexity and improving rendering performance.
WebTransport is arguably the most architecturally significant addition. It provides a modern, low-latency alternative to the aging WebSocket protocol, enabling full-duplex communication with multiple independent streams in a single connection. The practical applications are significant: real-time multiplayer games, collaborative document editing, live video conferencing, and financial data streams all stand to benefit. WebSocket was designed over a decade ago and carries design limitations that WebTransport was built specifically to address.
Keyboard Lock API rounds out the major additions. It allows web applications to capture keyboard shortcuts that browsers normally intercept — including Escape, Alt+Tab, and Ctrl+W — which is essential for web-based games and remote desktop applications. Without this API, a player pressing Escape in a browser-based game might accidentally close a dialog or exit fullscreen rather than performing the intended in-game action.
The 191 Bug Fix Effort
The sheer volume of fixes in this release reflects a deliberate strategy rather than accumulated neglect. Apple's team catalogued categories of cross-browser inconsistencies and worked through them systematically. Areas addressed include SVG rendering edge cases, HTML table layout behavior, MathML equation formatting, CSS Zoom handling, and a range of specification compliance gaps where Safari's behavior diverged from what the Web Platform Test suite defines as correct.
This matters because browser inconsistencies force developers to write conditional code, maintain browser-specific stylesheets, or simply avoid features that don't work reliably across engines. Each fix in this release reduces that tax on development teams maintaining production web applications.
What Developers Can Use Today
For developers working on production sites right now, CSS Grid Lanes opens up layout patterns that previously required third-party libraries or JavaScript. The feature enables Pinterest-style masonry grids, unequal column layouts in image galleries, and variable-height card arrangements that adapt fluidly to different viewport sizes — all expressed in pure CSS.
WebTransport support means developers building real-time features no longer need to choose between the limitations of WebSocket and the overhead of HTTP polling. The API supports both reliable ordered streams and unreliable datagrams in a single connection, letting developers pick the right delivery model for each data type in their application.
The Keyboard Lock API completes a capability that web game developers have been requesting since the earliest days of browser-based gaming. Combined with the Fullscreen API and Pointer Lock, it finally gives web applications the same input control that native applications have always enjoyed.
Looking at the Deprecation
The single deprecation in this release removes the FontFaceSet constructor from the CSS Font Loading API. This constructor was non-standard and not part of the specification, meaning no other browser ever implemented it. Sites that happened to call it would not have seen cross-browser behavior anyway, so the practical impact of its removal is minimal. Apple's practice of clearly flagging even minor deprecations in release notes reflects an ongoing commitment to giving developers time to adapt before behavior changes reach production.
Context Within the Browser Landscape
Safari has historically attracted criticism for slower feature adoption compared to Chrome and Firefox. This release signals a period of more aggressive alignment with the broader web platform. The combination of 44 new features and 191 fixes suggests a team that has been building toward this release cycle for some time, and developer survey feedback appears to be genuinely influencing what ships and when.
For users, most of the changes in Safari 26.4 will be invisible in day-to-day browsing — they show up as websites that load faster, render more accurately, or offer interactive features that previously only worked in other browsers. For the developers building those sites, the release represents a meaningful reduction in the cross-browser testing burden that has defined web development for decades.
This article is based on reporting by 9to5Mac. Read the original article.
