Repository navigation
[css-typed-om] Canonical units in computed values #725
Description
If I have an element with width: 1cm, then does its computed value reify to CSS.cm(1) (which serializes to pixels)? In CSSOM, we only need to deal with canonical units because serialization uses canonical units, but I think this doesn't apply to reified objects in Typed OM?
If this is the required behaviour, then AFAIK this is difficult to implement in Blink because we don't retain unit information in computed style. I don't know about the other browsers.
Activity
tabatkins commentedon Mar 5, 2018
I have no particular opinion on this. I'm fine with saying that computed value process uses canonical units.
upsuper commentedon Mar 11, 2018
I don't think Gecko preserves unit information for computed value either, so I also agree that it's probably better to use canonical units there.
[css-typed-om] Support animation and transition properties.
[css-typed-om] Support animation and transition properties.
[css-typed-om] Support animation and transition properties.
[css-typed-om] Support animation and transition properties.
[css-typed-om] Support animation and transition properties.
Bug 1449403 [wpt PR 10202] - [css-typed-om] Support animation and tra…
Bug 1449403 [wpt PR 10202] - [css-typed-om] Support animation and tra…
Bug 1449403 [wpt PR 10202] - [css-typed-om] Support animation and tra…
Bug 1449403 [wpt PR 10202] - [css-typed-om] Support animation and tra…
[css-typed-om] Reifying computed numeric values uses the canonical un…
Bug 1449403 [wpt PR 10202] - [css-typed-om] Support animation and tra…