W3C home > Mailing lists > Public > public-css-archive@w3.org > April 2019

[csswg-drafts] [css-values-4] How to serialize calc(100% - 100% + 1em) at computed-value time (#3806)

From: Gérard Talbot via GitHub <sysbot+gh@w3.org>
Date: Thu, 04 Apr 2019 21:03:30 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-429482172-1554411809-sysbot+gh@w3.org>
TalbotG has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-values-4] How to serialize calc(100% - 100% + 1em) at computed-value time ==
[§10.7. Computed Value](https://drafts.csswg.org/css-values-4/#calc-computed-value) states:

> calc(100% - 100% + 1em) resolves to **calc(1em + 0%)**, not to **1em** 

https://drafts.csswg.org/css-values-4/#calc-computed-value

but shouldn't that be instead:

"calc(100% - 100% + 1em) resolves to **calc(0% + 16px)**, not to **16px**", assuming 1em = 16px ?
Either this is the case or last parg of Example 35 (following below) misleads and creates confusion.

> A value like `calc(20px + 2em)` would serialize as `calc(2em + 20px)` as a specified value (maintaining both units as they’re incompatible at specified-value time, but sorting them alphabetically), or as something like 52px as a computed value (**em values are converted to absolute lengths at computed-value time**, so assuming 1em = 16px, they combine into 52px, which then drops the calc() wrapper.)


Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3806 using your GitHub account
Received on Thursday, 4 April 2019 21:03:36 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:31:06 UTC