Passkeys do not only ever live on one device that you then have to have with you. They sync across devices, just like passwords do — in a password manager. Check out what my team has created to explain passkeys. They are far superior to passwords!
27.02.2026 20:26 — 👍 3 🔁 0 💬 1 📌 0
Did you see what’s in Safari Technology Preview 238?!
* Customizable <select>
* Scroll anchoring
* The :open pseudo-class
* Threaded animations
* JSPI for WebAssembly
and more — including fixes for SVG, tables, WebRTC…
webkit.org/blog/17848/r...
Why are we *required* to let you sell our personal data to advertisers & data brokers? I will not agree. So I cannot attend?
25.02.2026 17:56 — 👍 1 🔁 0 💬 2 📌 0
We’ve been super focused on fixing gotchas. We had min(), max(), and clamp() since March 2020. And we had srcset and sizes attributes for img since 2014. But you couldn’t use min(), max(), and clamp() inside of sizes. Now, you can.
Like that. We’ve been obsessed with such things. Obsessed.
They are all new in Safari 26.4 beta!
developer.apple.com/documentatio...
* Auxiliary mouse button values in MouseEvent.button
* lighter operator in SVGFECompositeElement
* WebAuthn CTAP PIN/UV Auth Protocol 2
* Multiple microphone capture on macOS
* WebRTC network slicing on iOS
* MediaDeviceInfo in secure contexts
* math-depth
* font-size: math
* math-style and math-shift animation
* CSS size containment in MathML elements
* cursor property on ::marker pseudo-element
* CSS Zoom inheritance fixes
* customelementregistry content attribute
* CustomElementRegistry.prototype.initialize
What do these API have in common?
* WebTransport
* Keyboard Lock API
* Grid Lanes w/ flow-tolerance
* Threaded scroll-driven animations
* WebAuthn PRF extension
* ReadableByteStream
* Blob.stream() with BYOB reader
* Name-only @container queries
* min(), max(), and clamp() in <img> sizes attribute
Did you see? The first beta of Safari 26.4 is out today.
What’s most exciting to you as a person making websites/apps?
developer.apple.com/documentatio...
How have you not yet met my dog. She’s the most outgoing soul I’ve known. Beyond friendly.
17.02.2026 01:11 — 👍 1 🔁 0 💬 0 📌 0
Another episode of Unraveled: Understanding Complex Illness posted to YouTube. Please share, subscribe, comment, and most of all I hope it is helpful and educational.
youtu.be/NGbJWUp2ipU
The main features are well supported, passing all the tests.
The new area is only & specifically about 3 new extra superpowers. IMO, it should be called “Dialog & popover additions”. It’s NOT the whole feature. Just new bits.
Read our article on WebKit.org for the details.
@kevinpowell.co I’m listening to your podcast episode about Interop 2026. Congrats on getting it out so soon! I hear you wondering about “Dialogs & Popovers” support in Safari. It’s wrong to think that means our implementation of dialog and popover is poor. Nope! The focus area name is confusing 🤪
14.02.2026 03:37 — 👍 9 🔁 0 💬 1 📌 0
Grid: for creating containers for fluid content to fill
Flexbox: for stacking rigid blocks of content in the most efficient way possible
Does this even make sense?
Intuitively, grid is rigid and flexbox is fluid. But it's the other way around for their contents?
???
#vagueCSS
You nailed it!
webkit.org/blog/17818/a...
I’m particularly excited about media pseudo-classes in Interop 2026. Did you know Safari has had pseudo-classes for years — like :playing, :paused and :muted. Combine with :has() to style anything on the page depending on the state of <audio> or <video> playback. Now every browser will get support!
12.02.2026 17:07 — 👍 5 🔁 0 💬 0 📌 0
Interop 2026 launches today! If you want know on what it includes and what it means for web development — our article provides all the details. webkit.org/blog/17818/a...
Focus areas include Anchor Positioning, Style Queries, contrast-color(), WebTransport and much, much more.
I’m seeing so much about LLMs in my feed today.
Web designers and developers — how are you feeling about AI and what it means for your work?
Are you using the tools? How? What’s changing?
How do you expect AI to be used in the future for making websites & web apps?
Safari 26.3 is here with Zstandard file compression, Navigation API’s AbortSignal for better control in single-page apps, and fixes for anchor positioning, multi-column layouts, & more. Plus fullscreen video now dims surroundings in visionOS.
webkit.org/blog/17798/webkit-features-for-safari-26-3/
Two browser windows with card grids: masonry on the left, regular grid layout on the right, under “When will CSS grid lanes arrive? How long until we can use it?” title.
CSS grid lanes are arriving sooner than you think. @jensimmons.bsky.social says Safari Technology Preview has the finalized syntax, while Chrome and Firefox are close behind. Meanwhile, you can use @supports for progressive enhancement and a CSS or JS polyfill fallback.
webkit.org/blog/17758/w...
I mean, looking at the layout of this page I’m on right now — bsky.app/profile/jens...
There are 170 Flexbox containers.
And 0 Grid containers.
Why?
I see perfect user cases for Grid. Yet… zero?
Are you using CSS Grid? If you write CSS & code layouts on the web, and not using Grid — why not?!?
I see so many sites that still use only Flexbox for 100% of their layout. 0% Grid.
Why?
What would help?
I hear people say it’s hard. Is it? What’s hard?
What do you want to learn about CSS Grid?
When will CSS Grid Lanes arrive? How long until we can use it? from @jensimmons.bsky.social on the webkit blog
webkit.org/blog/17758/w...
It’s in Safari 26.0!
developer.apple.com/documentatio...
Oh yay!
Is there a video of your presentation? I’d love to see it.
I should say I totally understand if everyday developers have errors in their teaching. I mean, it happens. It’s when the big teams, the big pro heroes get it wrong, repeatedly…
And help teach the real version, now that it’s here!
Create your own demos.
Write your own articles.
:D
Help spread the word about what’s coming to browsers. And help make sure that the older ideas fade away into the distance, not get caught up in SEO/LLM as “truth”, confusing future developers.
Grid Lanes is easy! It's easy to learn, easy to use.
Please don’t get overwhelmed by the amount of contradictory teaching. Otherwise we’ll be stuck with the kind of mess we experienced with Flexbox… not knowing which advice to follow, with so many conflicting tutorials about how to use it.
Meanwhile, webkit.org is correct. We test our code samples with running demos. We clearly describe tentative ideas as tentative. We updated with notes.
I really don’t want you to be confused. I don’t want misinformation spreading. I don’t want LLMs to ingest out-of-date ideas & state them as truth.
Sure, there were lots of ideas being discussed & debated. But I see articles teaching how-tos as if tentative ideas were the final syntax. I sincerely hope people will either update their writing, or put a note on it explaining it was never the official spec & you should go learn elsewhere.
23.01.2026 22:08 — 👍 4 🔁 0 💬 1 📌 0
It’s wild to me just how much wrong information there is out there (written by humans in the later half of 2025) about using CSS to create masonry layouts.
There is no property named `grid-lanes` (as in grid-lanes: repeat(4, 200px)). There is no `masonry-direction` property. Or `masonry` anything.
