- From: Gérard Talbot via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Mar 2019 02:34:29 +0000
- To: public-css-archive@w3.org
TalbotG has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-values-4] Should physical units in specified values in calc() collapse into px unit when serialized? == > 5.3.1 Compatible Units > When serializing computed values, compatible units (those related by a static multiplicative factor, like the 96:1 factor between px and in, or the the computed font-size factor between em and px) are converted into a single canonical unit. Each group of compatible units defines which among them is the canonical unit that will be used for serialization. coming from https://www.w3.org/TR/css-values-4/#compat Now this test: http://www.gtalbot.org/BrowserBugsSection/CSS3Values/calc-serialization-specified-values-789.html I created this issue because no browser does what the current version of the spec explains. All 3 tested browsers will combine the terms 1in + 1pc into 112px. Isn't such combination going to confuse or disorient or irritate web authors? All 3 tested browsers will convert the term 25.4mm to 96px. Same question. All 3 tested browsers will *not* convert the term 25.4q to 24px. All 3 tested browsers will *not* convert the term 1.27cm to 48px. I do not have MS-Edge 18 so I can not verify... but you can see its results in a very similar test: https://wpt.fyi/results/css/css-values/calc-serialization-002.html?label=master MS-Edge 18 just like Safari 77 Preview do *not* support q unit. Finally, I have read https://lists.w3.org/Archives/Public/www-style/2016Mar/0331.html https://lists.w3.org/Archives/Public/www-style/2016Mar/0422.html and https://lists.w3.org/Archives/Public/www-style/2016Apr/0093.html Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3741 using your GitHub account
Received on Tuesday, 19 March 2019 02:34:31 UTC