Subscribe
Public posts from @bramus@front-end.social
btconf 2026 speakers
QQ about Dark Mode Toggles on websites
How many options do you show to users?
- Three values: System, Light, Dark
- Two values: Light, Dark (with one of them mapping to “System” behind the scenes).
Why the one or the other?
(I have an opinion about it, but I’m looking for external input)
TIL: @mdn exposes up-to-date page view data through https://popularities.mdn.mozilla.net/current.csv
Here’s a visualizer I had AI Studio throw together for me: https://ready-unit-fowl.codepen.app
👀 https://github.com/WebKit/WebKit/pull/70569
“Implement at-rule function for use with @supports”
See https://brm.us/at-rule for the details on this one.
We already did an initial pitch of this at @cssday back in June, and a quick read of the room confirmed we were on to something.
More feedback can’t hurt of course, so please reach out (or leave a comment at the CSSWG issue) if you have _any_ feedback 😊
In https://brm.us/styling-the-navigation I jotted down a quick intro to the concepts that we’ll be introducing:
1. Define Routes with @route
2. Query the navigation with @navigation
3. Select the navigation trigger with :nav-source
4. Advanced link selection with :link-to()
(And url-pattern() woven throughout)
I built a thing this week (with the help of Antigravity): a CSS Typed OM polyfill.
It currently passes 12588 of WPT's 12942 CSS Typed OM test, which is more than any browser!
New in Chrome DevTools in Chrome 151 (which goes stable mid July):
The specificity bubble can now show you a breakdown of how the specificity was calculated.
Big thank you and congrats to januschka.com for contributing this to Chromium 👏
@marcthiele “I love the shape of Bramus’ talk. […] It goes looking for the edge on purpose, shows you the failures along the way, and comes back with both a real tool and a grin. That is about as beyond tellerrand as a talk about a CSS specification can get. ;)”
Thank you, Marc.
On the Beyond Tellerrand blog you can find an accompanying write-up, written by conference organizer @marcthiele
https://beyondtellerrand.com/blog/btconf-dusseldorf-2026-video-bramus-van-damme
I am moved by the kind words Marc had to say about my talk. It proves, again, that he is one of the kindest and warmest persons I have ever met.
RE: https://mastodon.social/@btconf/116843238015514133
It’s video release week!
After the recording from All Day Hey and CSS Day before, the recording from Beyond Tellerrand is now available too.
While the talk is technically the same, the flow of it as well as its contents are quite different from those other renditions, so you might want to give this one a watch as well.
With #GoogleIOConnect Berlin just last week, my pre-summer conference season has come to a close.
In 2 months I did 4 Meetups, 5 Conferences, and 1 Team Summit … while doing some _actual work_ in between 🫨
This week I’m tying up some loose ends, and after that I’ll be taking some time off 🏝️
“Support colorspace and alpha attributes on <input type=color>”
Available for testing behind the Experimental Web Platform Features flag in Chrome Canary, starting tomorrow.
New Blog Post: “Do Websites Need to Function Exactly the Same on Every Platform?”
https://www.bram.us/2026/06/21/do-websites-need-to-function-exactly-the-same-on-every-platform/
(Betteridge’s Law of Headlines applies)
New Blog Post:
View Transitions: Should you use the new `attr()` or `match-element` for the `view-transition-name`?
Well … It Depends™
https://www.bram.us/2026/06/19/view-transition-name-attr-or-match-element/
New demo: Animated CSS Grid Layout.
https://codepen.io/bramus/pen/ogBYjgm
Here’s the thing, though: No View Transitions. Heck, no JS at all!
Instead, it uses Anchor Positioning to anchor the cell contents to the cell. Then, CSS transitions are used to animate the contents to their new location as the grid re-layouts.
Here's that calc-size() article @argyleink mentioned just now.
https://developer.chrome.com/docs/css-ui/animate-to-height-auto
Animate to `height: auto` is possible nowadays!
Excited for this talk by @argyleink.
I got a sneak peek yesterday, and this is gonna be gooooodddd! 🤩
Here's that issue about overscroll areas that @Una just mentioned.
https://github.com/openui/open-ui/issues/1457
I feel like they should probably be defined in CSS. See the issue for my reasoning here.
@nomster We want your feedback! Write a blogpost, send me a message, etc.
Very eager to hear what your use cases and needs are here 😊
At #CSSDay, we (@nomster and I) did a first public pitch of something we are currently prototyping: a way to add styles based on the active navigation.
Handy for View Transitions, and a few other things.
https://drafts.csswg.org/css-navigation-1/ is a WIP spec, with some bits implemented (behind a flag) in Chrome.
There, I fixed it:
:root {
--masonry: grid-lanes;
}
.container {
display: var(--masonry);
}
YES, Dark Mode Toggles _should_ be a browser feature.
I wrote about this before: https://brm.us/dark-mode-override
Find the link to the Chrome Bug in the post, and hit the star next to it to "upvote" the bug.
If you liked Jelle's talk and want to revisit, I have a small section on value processing on my blog (as part of a post on IACVT): https://brm.us/value-processing
CSS Day, day 1. #cssday
CSS DevRel, The Reunion. #CSSDay #ChromeDevRel
Caption: @argyleink, @Una, and I.
#cssday, day 0.
Tomorrow's gonna be a day of travelling + some meetings at the NL office + setting up our booth at the venue + pre-conf speaker dinner + a final rehearsal (and some last minute changes to the deck)
On Thursday the it's showtime 🤩 #cssday
Ready for this! #cssday
