- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Sun, 05 Jun 2022 17:07:10 +0000
- To: public-css-archive@w3.org
> I think the intent is to limit to 6 significant digits, not to 6 decimals. Is it correct? No, it means six digits after the decimal point. An integer in the millions shouldn't start rounding off its lower integer digits. > Does it refer to Number.toPrecision() as the serialization of JS to match? No, we were referring to the normal JS serialization of numbers, aka what happens when you stringify, as in `num + ""`. > What is the purpose of serialization in the shortest possible form? Is it to optimize the internal storage of values? No, serialization has nothing to do with internal storage, it's just what people expect out of serialization by default. When they write `1` they don't expect it to come back out as `1.000e0`. > Lastly, this resolution only applies to <number> and not to <integer>, isn't it? Then this issue does not justify modifying Syntax to produce a <number-token> with a type equal to integer in some cases where scientific notification is used, isn't it? The resolution doesn't pertain to that question at all; it's a separate topic. *If* the serialization I end up defining *does* use scinot for large integers, tho, then it still requires me to make some scinot strings parse to integers. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6471#issuecomment-1146849843 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 5 June 2022 17:07:11 UTC