You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We just resolved to add "infinity", "-infinity", and "NaN" keywords to calc(), to aid in serializing infinite/NaN values.
It's obvious that, like in the rest of CSS, these are recognized ASCII case-insensitively; "InFiNiTy" is perfectly valid and produces an infinity value. But what casing should we serialize these values with?
I think it's reasonable to mandate that "NaN" is serialized with that exact casing. It's a weird term, and it's always spelled that exact way; I've never seen it written as "nan", which is what you'd get from the default keyword-serialization rules.
I'm less sure we should do anything for the infinities. Javascript happens to spell them with an initial cap, as Infinity and -Infinity, but this isn't remotely a universal practice. I think we can get away with these serializing per the normal rules, as "infinity" and "-infinity".
I've currently written the spec to reflect these two; if nobody objects we can just leave it as I wrote it.
The text was updated successfully, but these errors were encountered:
We just resolved to add "infinity", "-infinity", and "NaN" keywords to calc(), to aid in serializing infinite/NaN values.
It's obvious that, like in the rest of CSS, these are recognized ASCII case-insensitively; "InFiNiTy" is perfectly valid and produces an infinity value. But what casing should we serialize these values with?
I think it's reasonable to mandate that "NaN" is serialized with that exact casing. It's a weird term, and it's always spelled that exact way; I've never seen it written as "nan", which is what you'd get from the default keyword-serialization rules.
I'm less sure we should do anything for the infinities. Javascript happens to spell them with an initial cap, as
Infinity
and-Infinity
, but this isn't remotely a universal practice. I think we can get away with these serializing per the normal rules, as "infinity" and "-infinity".I've currently written the spec to reflect these two; if nobody objects we can just leave it as I wrote it.
The text was updated successfully, but these errors were encountered: