davidmead
In reply to
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. .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
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. .It’s great to see the evolution of HTML happening in response to real use-cases—the turbo-charging of the select
element just gets better and better!
CSS wants you to build a system with it. It wants styles to build up, not flatten down.
Truth!
Technology doesn’t have to be terrible. Here’s an absolutely wonderful use of an e-ink display:
I made as much use of vanilla HTML and CSS as possible. I used a small amount of JavaScript but no framework or other libraries.
I like the approach here: logical properties and sensible default type and spacing.
I really like the way that the thinking here is tied back to Bert Bos’s original design principles for CSS.
This is a deep dive into the future of CSS layout—make a cup of tea and settle in for some good nerdiness!
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.