Jen SimmonsSafari 26.4 is here!
https://webkit.org/blog/17862/webkit-features-for-safari-26-4/
Grid Lanes. WebTransport. Keyboard Lock API. And _tons_ of fixes & improvements. Please read the introduction to our article to learn what we’ve been up to…
The heart of this release is focused on what web developers ask for most. We hear you loud and clear. Results from 2025 developer surveys made it clear you want time to catch up with new features, not be swamped with more. You want existing features to work consistently across every browser. You asked for browser engineers working on WebKit to help you by squashing bugs and closing gaps in spec coverage. That’s what this release aims to do.
Most features listed in Safari 26.4 release notes are not new. Many update features where the behavior didn’t match the latest web standard. Others make combinations of existing features work better together… we shipped support for the CSS `min()` and `max()` functions in 2018, almost two years before any other browser… and the HTML `sizes` attribute for responsive images back in 2014. But you couldn’t use `min()`, `max()`, or `clamp()` inside of the `sizes` attribute in WebKit. Now you can.
And then there are the bug fixes — hundreds of them across the platform. WebKit engineers went deep to improve specific areas like SVG, Tables, MathML, and CSS Zoom. And we’re continuing our multi-year rewrite of the layout engine. Blocks-in-inline layout is complete in Safari 26.4, work on Flexbox continues, and we’ve now begun rewriting CSS Grid.
As we continue this work, we greatly value your input. If something has been bothering you, it’s worth testing in Safari 26.4 to see if it’s been fixed. If the bug is still there, please file it at bugs.webkit.org. Or if it’s already filed, add additional comments to the existing issue describing your experience and why fixing it matters for you.
When multiple websites signal that something needs fixing, that helps. The more concrete you can be — a brief story about why this hurts your users, a link to a real website affected, a snippet of code or reduced test case — the better equipped we are to prioritize and fix what matters most. We are paying attention, even if our response shows up as a shipped fix rather than a reply in the issue.
We care deeply about the experience people have when using Safari. And we care about the experience people have when using any of the millions of iOS, iPadOS, macOS, visionOS, and watchOS apps that are built using WebKit and JavaScriptCore.
When our customers open a news app, a shopping app, a travel app, a banking app — there’s a good chance the interface they’re interacting with is powered by the same HTML, CSS, and JavaScript you write every day when making web apps and websites that live at a URL. Every rendering fix, every improved feature, every performance gain we ship benefits everything touched by the web platform.
We are passionate about making experiences our customers love, no matter how they use their device. Web designers and developers are central to those experiences. You are our partners. We truly hope this release makes a real difference in your success.
Steve@jensimmons thank you!
Marius Gundersen - mdg 🌻@jensimmons will any of these features be in an iOS 18.x release? We still see a lot of users on 18, not 26 yet
Jeremy Keith@jensimmons This is a real howler of a bug:
https://bugs.webkit.org/show_bug.cgi?id=305719
The supposed fix seems to have completely misunderstood the problem:
https://github.com/WebKit/WebKit/pull/60576
Right now the datalist element is completely unusable on iOS 26. That’s …really, really, really bad.
@jensimmons can you please fix this issue? All UIs with autocomplete or the text field at the bottom of the page are broken on iOS
LorenAmelang@jensimmons Jen,
My iPad (12.9, 5Gen) Safari has been nearly unusable since before iOS 26 appeared. I updated to original 26 hoping it might fix Safari, but no. I just updated to 26.4 and still have the same issues.
Just now I used "Find on Page" on an ASUS web page, it found no hits, but locked up. Nothing anywhere on the screen responded to clicks. I drug it off the apps screen and restarted it, it drew my custom home page, but that was unresponsive. Drug it off again, and the start page worked.
But it seems random. Sometimes I can go for several minutes, sometimes every change I make to the page locks it up. Find, swap to another open tab, click a link, enable Reader mode... I have no idea how to usefully report this to your bugs.webkit system. But clearly 26.4 hasn't fixed it. Do you have any thoughts on what I could do about this?
My other browsers, Vivaldi and Firefox, occasionally show similar lockups, but hours apart instead of seconds. I wish Safari worked, because it runs the Dark Reader add-on, which my lousy vision really needs!
Brooke Vibber 
@jensimmons loving every word of these release notes <3 works-everywhere standards compatibility is everything <3 <3 <3
Curioso 🍉 🇺🇦 (jgg)Congratulations, it is a really, really good idea.
The thing we web developers need most nowadays is stability and total compatibility between browsers. Nothing else is nearly as important.
There is no chance I am going to use any not fully cross-browser feature, unless I have no other option. It would make my work harder with no real advantage.
Even worse, here in Europe the demand for Safari compatibility is small, so there is no sense in using Safari only features. Safari users will much better served by these changes.