andruud
andruud
Yeah, it's weird that the order is reversed. Is that intentional @fantasai? Especially since we don't disallow block/inline/etc from <custom-ident>, so: - `view-timeline:block` creates a timeline named `block`, with the...
@emilio Your proposal sounds good to me. Having to expose `src` and other descriptors on `.style` (etc) feels like a design failure, so it's a bit annoying. (Though maybe not...
CSS-wide keywords [need to be the cascaded value](https://drafts.csswg.org/css-cascade/#initial), which they won't be in this case. So putting CSS-wide keywords in such a function doesn't work with the current model. Not...
I tried to find reasons why that would be annoying to implement, but can't think of any. So ... sounds good?
_That_ however, _is_ complicated, because it adds new and arbitrary dependencies between things that previously couldn't depend on each other.
> I think that Chrome's behavior is because it stores props with var() references as a token stream (throwing away comments) Yeah, that's right. Since we (should) serialize `--color: /*...
Adding `:container` probably exceeds acceptable complexity limits. It makes invalidation much more annoying, since we would need to figure out if a given selector _would have matched_ without `:container` pseudos,...
Nope, I don't have access either. (I'm also not an editor of this spec).
@laurentperez It is indeed not supported. Neither are <transform-function>/<transform-list>. The reason is certain details regarding these types are not spec'd (or not spec'd well enough). Hence we chose to ship...