Post

⌨️ I blogged about what I’d like to see come to #CSS in 2025. Some of my wishes are repeats from past years, but it was nice to see how many past wishes have (or are about to) come true! meyerweb.com/eric/thought...

meyerweb.comCSS Wish List 2025Back in 2023, I belatedly jumped on the bandwagon of people posting their CSS wish lists for the coming year. This year I’m doing all that again, less belatedly! (I didn’t do it last year because I c...

8/1/25, 4:34 pm16 reposts70 likes

tekno45.bsky.social

@tekno45.bsky.social

9 Jan 2025

I read this as CES lol.

Eric Meyer

@meyerweb.com

9 Jan 2025

Which is funny, because I just this afternoon misread a CES toot as being about CSS.

EIO

@eioluseyi.com

8 Jan 2025

Funny how I literally just came from your site, reading some older post

Bramus

@bram.us

8 Jan 2025

RE “Expanded attr() support”: It’s shipping in the upcoming Chrome 133 which goes early stable on Jan 29 (and rolls out to full stable over the course of a week) :)

Eric Meyer

@meyerweb.com

8 Jan 2025

Yep, I saw! That’s a great starting point. Here’s hoping it spreads to the other engines so I can cross it off my 2027 wish list.

Christoph Päper

@crissov.de

8 Jan 2025

With improved attr() in value space, I believe we also need better attribute selectors. github.com/w3c/csswg-dr...

github.com[Selectors] Numeric or Typed Attribute Value and Pseudo Attribute Selectors · Issue #354 · w3c/csswg-draftsThe CSS WG Wiki already mentions numeric comparisons of attribute values for Selectors Level 4 (or 5). @LeaVerou brought it back up in November 2015 and cites a post by @alastc from January 2007. I...