Romain Menke

Given the WPT tests I think it might make sense for `lightningcss` to avoid minifying as `u+a` but only to work around the Chrome bug. Not because it is actually...

There is also already a chromium bug related to those WPT tests : https://bugs.chromium.org/p/chromium/issues/detail?id=1215071&q=urange%20css&can=2 Leaving it up to you to ignore this issue or maybe apply a patch. I don't...

https://github.com/w3c/webref/issues/597#issuecomment-1165698931 > Some figures, quickly looking at sources: > > bcd defines 13717 features > Can I use defines 529 features > chrome platform status defines 2153 features > webkit...

@KaelWD thank you for your contribution! _The `next` version is not a more feature rich variant of the same polyfill but rather an updated version and this might be breaking._...

> Where is that quote from? It is not a quote, but my reasoning for being cautious here. The fact that the `next` version never became the main version indicates...

/ok-to-test sha=a12066d Tests running at https://github.com/Financial-Times/polyfill-library/actions/runs/3027449751

I think you can do this today with `:has()` but the ergonomics might not be ideal. _At least it is possible to polyfill/downgrade_ ```css /* using :where() for 0 specificity...

Nested shorthands could work with something similar as the grid syntax : https://developer.mozilla.org/en-US/docs/Web/CSS/grid-template-areas ```css @property --some-shorthand { syntax: "" " " ""; constituent-properties: color text-decoration display; values: ...; } ```

`/` is a bit ambiguous with ratio's (`aspect-ratio: 1/2;`) But maybe this is fine ``` / + ``` vs. ``` / ``` ----- The only purpose of the `/` between...

I remember seeing in multiple places that @tabatkins mentioned that mixins, `@include` and `@apply` will never be a thing. I however could not find the original reasoning behind it. So...