Three-way tie between temporal API, transition-behavior: allow-discrete, and anchor positioning, but tbh any one of those would be glorious

Similar to what others have said here already, some sort of query selector-like syntax would be suuuuper useful, especially for pointing to a sibling input.

E.g. something that says "hey this label is for the input next to it" like:
<label for="+input">...</label>
<input type="text" />

Hah, fingers crossed! Thanks for the excellent newsletter too btw, it's always a fun little rush when I see a new issue hit my inbox 🙂

Funny side thought while reading: it's a bit ironic how the link for #5 in the Table of Contents instantly jumps down to the section about using `scroll-behavior: smooth` 😉

On my android, goose and puffin both feel identical regardless of density, but toucan is significantly smoother 💪

Device: Galaxy S23
Browser: Firefox for Android (133)
Goose: 60
Toucan: 160
Puffin: 60

Yeah the grouping makes sense but it's the *ordering* of those groups that I wonder about

Like do you put the group of flex/grid properties before or after position properties, transform/transition properties, etc? Or group by size? Or base > components > utilities like Tailwind? Or just yolo it?

Genuine question: what would be the smartest ordering? Or something better than alphabetical?

I find myself using with alphabetical because it's immediately easy to locate the property I need and it's universally understood. Or maybe I've just been bitten by too much inconsistency with other ways 😅