Over the past years, I’ve written a bunch of posts and done quite a few experiments with View Transitions, such as optimizing the keyframes (so that they animate on the compositor) or driving a VT by scroll.
I noticed I repeated a lot of code while creating all those … so I bundled that all up in a package for you to use as well.
Optimizing the keyframes or a VT for example now is just a one-liner: optimize(transition);
Authorship lets you attribute parts of your text to different authors.
Clearly identify what you wrote and who else helped, including AI sources.
Try Authorship in Writer for Windows by joining the beta: https://ia.net/topics/who-wrote-this
Bram.us
• Bramus!
If you’ve ever tried to build a data table with a sticky header and a sticky first column, you know the pain. You’d think a simple position: sticky with top: 0 and left: 0 would be enough, but the reality was that only one of both would stick.
A recent change to CSS fixes this: position: sticky now plays nice with single-axis scrollers, allowing you to have sticky elements that track different scroll containers on different axes. This change is available in Chrome 148.
If you’ve ever tried to build a data table with a sticky header and a sticky first column, you know the pain: the reality was that only one of both would stick.
A recent change to CSS fixes this: `position: sticky` now plays nice with _single-axis scrollers_.
Hello my name is Niels Leenheer
• Niels
No, CSS is awesome. CSS is better than ever and it is only getting better. And that is why I built DOOM in CSS. Every wall, floor, barrel, and imp is a <div>, positioned in 3D space using CSS transforms. The game logic runs in JavaScript, but the rendering is entirely CSS. You can play […]
The post CSS is DOOMed appeared first on Hello my name is Niels Leenheer.
“More” I say?
Yes, I did an experiment with making an extension to debug Anchor Positioning before:
https://front-end.social/@bramus/116213083230487150
There's a lot of complexity involved to make it work accurately … so that one ain't public (yet?).
Some more prototyping fun: this time an extension to visualize the Containing Block of an element.
It shows the element and its containing block (an element, the Viewport, or the ICB) along with some base info.
Get it here: https://chromewebstore.google.com/detail/devtools-containing-block/cfhjohibdfclahlfljknkjmcdkfkcflj
What other info would you like to see in a feature like this?
(The heavy lifting to identify the containing block is done by the https://github.com/bramus/get-containing-block package which I also created for this)
RE: https://front-end.social/@leaverou/116297807826814028
Before you blindly say 100px–200px–300px, hear me out: https://github.com/LeaVerou/blog/discussions/137#discussioncomment-16340589
(And if you really want it to be 100px–200px–300px then it’s simple: don’t type the --arg)
iA
• iA Inc
Authorship comes to iA Writer for Windows
RE: https://mastodon.scot/@svgeesus/116280100248182454
More details on the “parsing would be hard” part in https://www.bram.us/2026/03/19/more-easy-light-dark-mode-switching-light-dark-is-about-to-support-images/ ;)
If you are in Tokyo, come see our Notebook in person at the Tsutaya Bookstore in Roppongi Hills, until April 7.
The Making of iA Notebook.
Follow along for a behind-the-scenes look at how our Notebook is made.
iA
• iA Inc
The making of iA Notebook
Bram.us
• Bramus!
CSS light-dark() is being extended to support images.
CSS `light-dark()` is about to support images!
Shipping in Firefox 150. Starting tomorrow, available behind a flag in Chromium 148.
Writing is hard work. Sometimes we can focus for hours without feeling any strain. Sometimes we feel exhausted before completing the first paragraph, and we don’t know why. What can we do to get—and stay—in the flow?
(Don't) get wet.
Today we set up a new iA pop-up at Tsutaya Roppongi.
Bram.us
• Bramus!
Back in January 2022, I wrote about an exciting new CSS Working Group decision: a function to detect at-rule support using @supports at-rule(@keyword). Fast forward to today, and the CSS Conditional Rules Module Level 5 specification has solidified how this feature works and Chromium (Chrome, Edge, etc.) is about to ship it in Chromium 148!
New in Chromium 148: detect at-rule support in CSS with `@supports at-rule(@keyword)`
https://www.bram.us/2026/03/15/at-rule/
Chrome 148 is currently available on the Canary and Dev release channels. It goes stable at the end of April.
