I finally came around to writing up the details behind the CSS-only code listings I use on my blog. These listings wrap on page resize with line continuation markers, show scrollbars past a configurable minimum width, support native text selection without the line numbers being copied, and number lines in plain CSS without any JS involved. Have a look, the post is simultaneously a demo:
#css
48 posts43 participants0 posts today
Public CSS Custom Properties in the Shadow DOM, by @michaelwarren.dev:
michaelwarren.devPublic CSS Custom Properties in the Shadow DOMThe definitive guide to using public CSS Custom properties to configure web components externally. Surely no one will ever write about this topic again.
Continued thread
To support some basic personalisation you can set the accent colour. That colour is used as the base for all other colours. All via CSS (there's a little bit of JS used to make it update live on the settings page).
It's time for modern CSS to kill the SPA
Link: https://www.jonoalderson.com/conjecture/its-time-for-modern-css-to-kill-the-spa/
Discussion: https://news.ycombinator.com/item?id=44688489
Jono Alderson · It's time for modern CSS to kill the SPANative CSS transitions have quietly killed the strongest argument for client-side routing. Yet people keep building terrible apps instead of performant websites.
Can anyone explain to me how #tailwind somehow doesn't suffer from all the same problems as traditional inlined #css using the style attribute?
Only argument I've seen right now is that tailwind can make use of things like ::after or target child elements, but none of that stuff has ever been the reason why inline style fell out of fashion.
Am I missing something, or is it really just a new generation of developers repeating the mistakes of the past and doomed to find out eventually?
“Browsers are evolving to reward simplicity and resilience. They’re building for the kind of web we should have been embracing all along.”
https://www.jonoalderson.com/conjecture/its-time-for-modern-css-to-kill-the-spa/
Jono Alderson · It's time for modern CSS to kill the SPANative CSS transitions have quietly killed the strongest argument for client-side routing. Yet people keep building terrible apps instead of performant websites.
CSS masonry is going into developer trial (behind a flag) in Chromium. Learn how to test the implementation and give your feedback in this post from the Microsoft Edge team https://developer.chrome.com/blog/masonry-update #css
Chrome for DevelopersBrick by brick: Help us build CSS Masonry | Blog | Chrome for DevelopersHelp test the proposed masonry syntax in Chromium.
CSS Logical Properties—What, Why, and How, by @schalkneethling:
https://www.youtube.com/watch?v=cxSowU9sDdU
A neat video on the :has() css selector
Replied in thread
What #libre #IDE (integrated development environment for programming code) would y'all want to coalesce around using, supporting, and developing? Asking especially for coding websites and applications with #PHP, #JavaScript, #CSS, and #HTML but #Python, #Elixir, #Rust, and #Go would all be great for us @agaric too.
I've been exploring different ways to interact with a user preferred font size. Could the max() function work better than a classic px-to-em conversion?
Along the way: How Best Practice ruined text-only zoom! 
Still thinking about units & type in #CSS …
OddBirdDesigning for User Font-size and Zoom
More from 
Mia (web luddite)
Join me in NYC this October at SmashingConf!
I'll be giving both a workshop and a talk around #a11y and #css.
[20% OFF] using this link - plus a discount if you plan to attend both the workshop and conference (scroll for that option!)
https://ti.to/smashingmagazine/smashingconf-ny-2025/discount/IHopeYouWillBeJoiningMe
Did some maintenance work on my #Hugo #blog just now: combined all css into one bundle using a bundle-resource partial, trimmed out whitespace in <head> (looks much neater now) and removed fontawesome.
The number of requests is down and I feel the page loads way snappier (I could be biased lol). I just realise aliases in Hugo creates a lot of extra folders/files in /public. Once I check there's no new incoming traffic from those I'll delete it?
512KB/1MB club soon? 
Does the CSS font-family property use ”Name For Humans", "Family Name" or “Fontname” from the “PS Names” tab in FontForge’s “Font Information”?
My testing has been inconclusive. I first though it was “Family Name”, but noticed inconsistencies. Now I believe “Fontname” might be it. But it’s impractical, because Arial on one OS might have one “Fontname” and Arial on another OS might have another.
I should add that the LLMs hallucinate wildly on this question.
Tailwind is the Worst of All Worlds, https://colton.dev/blog/tailwind-is-the-worst-of-all-worlds/.
The article explains why Tailwind (https://tailwindcss.com/) is based on and encourages bad practices, which creates more maintenance burden and larger bundles. The article also explains why Tailwind met success and what other better tools should learn from that.
colton.devTailwind is the Worst of All WorldsApparently this horse hasn't been beaten enough.
Dynamic “nth-child()” Using “sibling-index()” and “if()”, by @css:
css-tip.comDynamic nth-child() using sibling-index() and if()
More from 
CSS by T. Afif 
CSS Masonry layout is almost here, and we want your help and feedback to finish it!
Chrome for DevelopersBrick by brick: Help us build CSS Masonry | Blog | Chrome for DevelopersHelp test the proposed masonry syntax in Chromium.
Tailwind is the Worst of All Worlds. #CSS #Failwind
Posted into Coding is Living @coding-is-living-mobileatom
colton.devTailwind is the Worst of All WorldsApparently this horse hasn't been beaten enough.