W3C home > Mailing lists > Public > public-css-archive@w3.org > February 2018

Re: [csswg-drafts] [css-values] calc() should round when it's used as an <integer>

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 28 Feb 2018 17:57:39 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-369325953-1519840658-sysbot+gh@w3.org>
The Working Group just discussed `[css-values] calc() should round when it's used as an <integer>`, and agreed to the following resolutions:

* `RESOLVED: Accept the proposal in #2337`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-values] calc() should round when it's used as an &lt;integer><br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2337<br>
&lt;dael> TabAtkins: Basic issue, when you put an invalid number in the calc due to range restrictions we clamp instead of call it invalid. But we try and track int or number to reject at parse time. If you do division it becomes a number. THis is inconvenient for typed OM. We'd like any numbers to work out.<br>
&lt;dael> TabAtkins: I think the distinction for int and number I wrote in is for conveince not a need. I propose if a prop only takes an int and calc in non-int we round to an int. We do this for animations already.<br>
&lt;dael> TabAtkins: To match how animations of int are specified at 0.5 we round up.<br>
&lt;dael> Rossen_: Any other opinions<br>
&lt;dael> Rossen_: Or suggestions<br>
&lt;tantek> that sounds like a reasonable proposal and way of re-using another approach of how we deal with this situation<br>
&lt;dael> AmeliaBR: I believe someone said edge does this?<br>
&lt;dael> TabAtkins: fremy said they do but they floor so he had a weak preference for that. I think match animations is better.<br>
&lt;dael> AmeliaBR: Yes, doing actual rounding sounds more logical.<br>
&lt;dael> Rossen_: Wouldn't disagree. For matching with flooring or animations I'd also prefer animations.<br>
&lt;dael> Rossen_: So I would be fine with TabAtkins proposal.<br>
&lt;dael> Rossen_: Any other ideas or suggestions? If not we can resolve to accept current.<br>
&lt;dael> Rossen_: Objections?<br>
&lt;dael> RESOLVED: Accept the proposal in #2337<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2337#issuecomment-369325953 using your GitHub account
Received on Wednesday, 28 February 2018 17:57:42 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:24 UTC