w3c/css-houdini-drafts

[css-typed-om] Make CSSUnitValue use unrestricted double

fantasai opened this issue · 1 comments

See discussion at w3c/csswg-drafts#8114 (comment)

Since CSS can now represent infinite and NaN values, Tab's proposal is to make CSSUnitValue use unrestricted double.

The CSS Working Group just discussed [css-typed-om] Make CSSUnitValue use unrestricted double.

The full IRC log of that discussion <flackr> discussion of who should take this
<flackr> fantasai: can we make progress without tab?
<flackr> bkardell_: tab had a proposed resolution
<Rossen_> linked resolution proposal: https://github.com/w3c/csswg-drafts/issues/8114#issuecomment-1458935503
<flackr> Rossen_: summarizes linked proposal
<emilio> q+
<flackr> bkardell_: TabAtkins believes this is fine for cssom because we have the needed types
<Rossen_> ack emilio
<flackr> emilio: plain css values in the computed space are not allowed to be +/- infinity so it's a bit weird
<flackr> emilio: you usually need a calc to have an infinity and it gets simplified to a large number when computed, so it might be a bit inconsistent
<flackr> emilio: has anyone looked into this?
<flackr> Rossen_: tab has, and thinks it's okay
<flackr> emilio: If you assign an infinite value to a style map with a specified value, what does it turn into? is it implicitly wrapped in a calc?
<flackr> emilio: it's fine, but perhaps a bit odd that you'd get a calc back
<flackr> Rossen_: this is the discussion we need to have, let's wait for TabAtkins to push this forward since there are concerns
<flackr> emilio: sg