Well, that's probably dead then.

Wait. What IPO?

CSS becoming more Javascript (aka: dynamic) is not really something that entices me. I'm worried many of these features can be naturally used to fingerprint visitors, which might in turn lead to something like a culture of anti-JS, but for CSS, like with CSS blocking lists for uBO etc.

Wait, I randomize everything on my sites and I like minimum JS, I'm so gonna love using this :O

edit: Fuck yeah! The more I read the article the more I like it :D

I get around this by only using optimised SVGs then inlining them.

Also note that this leaves out changes after compression—this was not part of the experiment but would be fair to test, too.

This seems extremely relevant actually because gzip/brotli use chunk deduplication as one of their core concepts.

cool

Scrollytelling

I hate you for this.

There is a CSS media feature for that prefers-reduced-motion.

How about less animation.

I always have found her highly opinionated (and sometimes even pedantic) but with interesting thoughts. However here I feel she's solving a problem that doesn't exist. Yes, the mask hack is still a hack and styling svg pseudoelements should be a problem that CSS should solve, but there is no better way to author icons than SVG. You can inspect them, tweak them, change them in any way you like with the aid of webtools in your browser as you would do with regular HTML. Moving all of that to the stylesheet just because "they are design tokens" just adds a huge layer of clutter to the already bloated modern CSS stylesheets.

1. Ditch javascript whenever possible

These are good, assuming you're taking the care to see which ones are supported.

Kevin Powell's youtube is worth a shoutout here since he has showcases of his and other's new techniques that become available because of these new rules (he's more interested in applications rather than new rules themselves).

Very cool. I used to make JS-free navigation menus by using a hidden checkbox for keeping the state of whether it should be displayed. Cool to see more proper APIs being introduced for this.

How we fully migrated github.com away from CSS-in-JS.

yay 🙌

It’s available in all relevant browsers since 2024 so there is not one single real reason to not use it.

I still prefer the prefers-color-scheme media query because it makes it easier to properly separate the color schemes in code.

I mean, light-dark is great as a function to have to enbrief specifically the use-case of light vs dark themes, but that duality is so limited I don't even use the function. I use media queries and prefers-color-scheme to be able to support arbitrary themes easily. This way I have to worry about compatibility far less, too.

Now that Safari has random() (and Chrome has it behind the Experimental Web Features flag),

https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Values/random

Chrome canary, Firefox nightly, experimental

Well, input[checked] already exists. Why wait for ::checkmark?

Lol clicked the link thinking it was a giant movie list colab list, then saw it was CSS styling and was disappointed. But to be fair I should have checked the thread it was posted on haha.

So tl;dr: we need UBI?

The demo doesn't seem to work on Firefox.

RIP Tailwind.

Then again, I was never one for CSS frameworks (or frameworks of any kind, really). So I won't be too sad about doing CSS by-hand, like Arceus intended.

the Shopify CEO is a nazi billionaire who has said voting rights should be based on how wealthy you are, and poor people should not get a vote at all.