Note: currently, it might not work in mobile Safari. I spent a few hours trying things, the latest dev deploy of my site worked, but the prod one does not.

If you cannot open it by the link about in Safari, a workaround that works for me (but still slow) is to go to https://kizu.dev directly and then go to the article.

Will investigate later again, but oh well. Sorry.

As usual, the credits:

- @argyleink, Jonathan Neal, Giorgio Pretto, Sebastian Malton & Oriol Brufau for CSSWG issues related to `sibling-index()` and `sibling-count()`.

- @tabatkins & Benjamin De Cock for CSSWG issues related to `random()`.

- Michal Čaplygin for an issue about tree-counting functions in Open Props.

- @heydon, @leaverou & @me for Quantity Queries.

- @leaverou and Alex Walker for the articles on cicada principle.

- @kevinpowell for his talk at CSS day.

[1/2]

As usual, credits:

- @5t3ph for her article about @property.
- @kevinpowell for his video about inheritance.
- @bramus for his post about feature detection.
- @Una for a CSSWG issue about named container query length units.
- @JaneOri for her `tan(atan2())` technique which I mention once again.
- @argyleink for Open Props (could this pattern be helpful to it?).

@kizu I feel the same way about the linked issue proposing to change how `prefers-color-scheme` to work. I think I’d have to rewrite some of my CSS mental models if that were to change. Seems less harmful to either use the style query approach you’ve demonstrated or for that to develop into its own specific query. Also, seems like style query support for at least some non-custom properties worth revisiting.

@kizu ha, i was working on a post about color-scheme too. this just means i have to write fewer things 😁

and totally agreed on the media queries behavior: media queries should reflect the user's preference, not the author's (even if that's set in HTML). https://front-end.social/@mayank/112763009752291121

@kizu oooh I love your new (?) aside components! have you talked about those already?

@kizu Love it!!

(oops, forgot to put hashtags for the post's announcement: #CSS and #Typography — here you go!)

For years, what I was mindlessly doing instead: applying a negative margin with “random” values of 0.2em-0.3em for cases like this, which, coincidentally, almost the same!

Intuitively, and by testing, I was pleased with these values all this time, but having a proper method on one hand, and a confirmation that this type of adjustment results in what the fallback ends up being in the end is nice, haha.