A bold proposal by Heydon to make the process of styling on the web less painful and more scalable. I think it’s got legs, but do we really need another three-letter initialism?
We waste far too much time writing and maintaining styles with JavaScript, and I think it’s time for a change. Which is why it’s my pleasure to announce an emerging web standard called CSS.
In reply to https://adactio.com/links/14129.
With quotes like For as long as anyone can remember, styling documents — affecting their appearance — has been facilitated via the JavaScript style property I can’t tell if it’s a joke or not. If it isn’t, I despair.This is clever: putting CSS inside a noscript element to hide anything that requires JavaScript.
A workshop on resilient CSS layouts
Oh, hell yes!
Do not hesitate—sign yourself up to this series of three online workshops by Miriam. This is the quickest to level up your working knowledge of the most powerful parts of CSS.
By the end of this you’re going to feel like Neo in that bit of The Matrix when he says “I know kung-fu!” …except kung-fu isn’t very useful for building resilient and maintainable websites, whereas modern CSS absolutely is.
If we were to follow Jiro’s and his apprentices’ journeys and imagine web development the same way then would we ask of our junior developers to spend the first year of their career only on HTML. No CSS. No JavaScript. No frameworks. Only HTML. Only once HTML has been mastered do we move onto CSS. And only once that has been mastered do we move onto JavaScript.
This looks like a really interesting proposal for allowing developers more control over styling inputs. Based on the work being done the customisable select element, it starts with a declaration of appearance: base.
And by LLMS I mean: (L)ots of (L)ittle ht(M)l page(S).
I really like this approach: using separate pages instead of in-page interactions. I remember Simon talking about how great this works, and that was a few years back, before we had view transitions.
I build separate, small HTML pages for each “interaction” I want, then I let CSS transitions take over and I get something that feels better than its JS counterpart for way less work.
Safari 18 supports `content-visibility: auto` …but there’s a very niche little bug in the implementation.
Try writing your HTML in HTML, your CSS in CSS, and your JavaScript in JavaScript.
A genuinely inspiring event.
Had you heard of these bits of CSS? Me too/neither!
If you’re going to toggle the display of content with CSS, make sure the more complex selector does the hiding, not the showing.