Tab Atkins Jr.

Ah dang, you're right. All my examples were single-node so I didn't notice the discrepancy. Yeah, auto-reversing doesn't actually work, since you'd have to reverse recursively in complicated sequences. Hrm....

Indeed, it is similar to AlternatingSequence, but I do want to highlight the "main" sequence over the repetition part, and AlternatingSequence doesn't do that. But maybe if we took that...

Any of these are possible, fwiw. Sometimes they're complicated to get right, but everything here is potentially doable. A benefit of the variant AlternatingSequence is it reduces the number of...

We certainly discussed it at the same time. If we didn't take an official resolution that was just an oversight; we should be moving both of them back under our...

I don't want to shove the existing descriptors into an unlabeled prelude space; that's hostile to future expansion, as we'd have to make sure the descriptor syntaxes either work together,...

Quick aside about the "computationally independent" - the reason for that restriction is to avoid authors having to think about what lengths like `3em` are resolved against, and how the...

> @layer (non-plural form) allows specifying multiple layers, so we could re-use @property (non-plural) to specify multiple properties. Hm, we do expose the two types of `@layer` as two different...

The problem is that ems (and similar) have rules for when they evaluate - you'll never see an em in a property you've inherited, in any property, custom or not....

The first one (multiple comma-separated names in the registration) we should definitely do, no question. Such an obvious improvement. The second (wildcard registration) is something I support if it's feasible...

Oh, but: > It should also be pretty easy to do, if it's just a parse time shortcut that is expanded into multiple rules for the CSSOM. It shouldn't be...