W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2020

Re: [csswg-drafts] [cssom] Is `round` special in CSSOM? (#5689)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 11 Nov 2020 17:54:16 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-725569391-1605117255-sysbot+gh@w3.org>
The CSS Working Group just discussed ``[cssom] Is `round` special in CSSOM?``.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [cssom] Is `round` special in CSSOM?<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/5689<br>
&lt;dael> chris: Context was I was going through cssom def os serializing color b/c moving to color 4. Had a special definition of rounding. Seems there is a reason, mainly for negative numbers, that you have to spec<br>
&lt;dael> chris: Do we want this in cssom or copy to color 4, assume rounding is rounding? I wanted guidance before I remove the section<br>
&lt;dael> TabAtkins: Legit question. confusing if round up means toward infinity or away from 0. Ideally shouldn't restate in algos and we should have a statement in OM about how to round<br>
&lt;dael> TabAtkins: Not sure if [missed] has a need<br>
&lt;TabAtkins> s/[missed]/Infra/<br>
&lt;dael> emilio: css values should have something about this b/c came up when dividing numbers<br>
&lt;dael> Rossen_: Had similar discussions around math functions and aligning to a particular language. Discussion around mod operator<br>
&lt;Rossen_> q?<br>
&lt;dael> TabAtkins: I suspect match JS b/c if someone were to impl on their own that's what would happen<br>
&lt;dael> TabAtkins: Apparently c++ and JS differ in default roundin gup<br>
&lt;dael> TabAtkins: Is it better ot match JS, C++, Rust or what?<br>
&lt;dael> emilio: Rust does C++ afaict<br>
&lt;dael> TabAtkins: So away from 0<br>
&lt;dael> fantasai: C++ probably makes more sense for CSS<br>
&lt;dael> Rossen_: Trying to avoid whole discussion about how to align better with math/js/other lang which is the discussion we had before which was heated and we kept coming back to it. I would suggest take this back to the issue and come back with a proposal<br>
&lt;dael> Rossen_: We could spend the next 7 minutes just shifting through languages<br>
&lt;dael> chris: Fine for me<br>
&lt;dael> fantasai: We were just talking values. Values 4 draft is super out of date<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5689#issuecomment-725569391 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 November 2020 17:54:18 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:22 UTC