[mediaqueries-4] change infinite in resolution descriptor to infinity to match css-values

[romainmenke]

https://www.w3.org/TR/mediaqueries-4/#resolution

@media (min-resolution: infinite) {}

@media (resolution = infinite) {}

@media (infinite = resolution) {}

@media (resolution < infinite) {}

@media (infinite > resolution) {}

As far as I know this is currently the only current media description that has a range type while also accepting an <ident> value (infinite).

I am assuming that the syntactical ambiguity is ok because browsers would have lists of known media descriptors.

In css-values the numeric constant infinity is defined.
Should this same constant be used here?

infinite -> infinity

In a range context this seems more intuitive :

@media (resolution = infinity) {}

@media (infinity = resolution) {}

@media (resolution < infinity) {}

@media (infinity > resolution) {}

---

Maybe this is a moot point since infinity is a numerical constant so should be allowed anyway with calc.

@media (resolution = calc(infinity)) {}

@media (calc(infinity) = resolution) {}

@media (resolution < calc(infinity)) {}

@media (calc(infinity) > resolution) {}

[romainmenke]

nvm, infinite aligns with the keyword used in transitions so also has a precedent.

[tabatkins]

Yeah, we ended up with the property-specific keyword form being "infinite", but it felt weird to have infinite be a numeric keyword for calc().

[Loirooriol]

Note that with calc you would need something like calc(infinity * 1dppx) in order to get a <resolution>, and this won't be the same as infinite as noted in https://drafts.csswg.org/css-values-4/#calc-range

Even properties that can explicitly represent infinity as a keyword value, such as animation-iteration-count, will end up clamping ±∞, as math functions can’t resolve to keyword values; the numeric part of the property’s syntax still has a minimum/maximum value.

[romainmenke]

relevant : #8998