Tab Atkins Jr.

In general, "special syntax to make something go first" isn't very composable. Things end up fighting over being first, the set of things putting themselves first still needs to establish...

Not necessarily equal number, but an equal sum-of-flex-basis, yeah. That way you don't end up with the frustrating scenario where you have twenty items, and nineteen of them fit on...

I just opened #12222 to see if we can fix that "flex items can be negative-sized for line-breaking" issue in general, but even if we can't, I agree that it's...

As expressed in the minutes today, I completely misunderstood what "Option 1" was, and take back my support of it from the earlier meeting. ^_^ What I *assumed* it was...

Hm, you're right. On further consideration, I don't think we *can* actually have forward-compat here, so long as we're doing a *search* for the container element. An older browser will...

The relevant change would be making `(unknown) or (width > 100px)` go from (potentially) matching to (always) skipping; the behavior for `(width > 100px) or (height > 100px)` (against an...

> The difference (as I understood it) between the comma vs the or is that the comma-separated queries could resolve on different containers – which is why I proposed allowing...

I strongly agree with @bakkot as a code author; I enjoy a good type pun as much as the next person, but passing a string to an API that expects...

> `""+foo` will throw if foo is a Temporal object because `valueOf` throws Interesting. That's definitely a challenge, then. Tho, in my limited experience with Temporal objects, you don't *really*...

I'd have to review to make sure that 'auto' doesn't have any special behaviors that make it incompatible with explicit lengths in some situations. That is, any place where the...