Tab Atkins Jr.

> does this go into the Web Apps working group? I think it's reasonable for this to graduate either to the CSSWG or the WebApps WG for standardization, with a...

IIRC, the "single token" thing was written in back in the day to simplify implementation; for whatever reason, impls didn't want to invoke their full CSS parser on attribute values....

Yeah, pre-ES5 those keywords were reserved unconditionally. But it's been a decade since they were usable for property access.

I'm slightly against this. The use-case is reasonable, but I think we should solve it more directly. Basically, a function knows exactly what variables *it* is going to use. There's...

> * We could drop `using`, treat the element variables as "global", and make them always available in all functions (shadowed by locals, obviously). > * Or, we could make...

> What if variable references that the function is not able to resolve are propagated and resolve at the point of calling? Would something like that work? If I'm understanding...

> Q: It would be nice if there was a JS API to add pure computational functions to CSS down the line. Would this preclude such an API? Not necessarily....

I don't think what we decide here has any relevance for closures later, actually. Functions as we're defining them simply *do not have a meaningful lexical scope* - they're defined...

It currently does only that, yes. My question is if it should be treated as doing *more*, because it communicates the color scheme at a level that is above CSS,...

> I don’t have an opinion (yet) on whether the meta value should affect the result of the MQ but if it does, then declaring color-scheme: dark on :root should...