Yves Lafon
Yves Lafon
Note that you don't need to support all of them, just have the name of the supported compression format be the same as the ones listed there.
Indeed, the definition of ratio in the css validator is way outdated. I opened an issue to track that.
Just to note that it was fixed upstream (see right above).
Just to reiterate, as negative values are in direct contradiction with the Gamepad spec, please work with them to figure out a way forward (allowing negative values with a "reserved"...
It is indeed related to handling variable types, which has been done in calc() but not here.
Note that having default value (then types) is a way to temporarily fix this. `x { --y: max(1 * var(--a, 2em), var(--b, 42px)) }` is shown as valid as the...
To me it is more a bug than en enhancement as the initial goal was what you described.
The example you give is not throwing an exception, at least not on https://jigsaw.w3.org/css-validator/#validate_by_input DO you have ways of reproducing this?
The padding issue, related to variables handling in clamp() has been fixed upstream. See https://github.com/w3c/css-validator/issues/412 `rotate`, CSS Transform Module 2 in general, is not implemented yet.
no issue for that, I'll create one unless someone beats me to it (it will be in a few hours)