- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Jan 2020 11:18:43 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Adding an infinity keyword`, and agreed to the following: * `RESOLVED: no non-ASCII in Core CSS` * `RESOLVED: add infinity and nan as new css math constants` <details><summary>The full IRC log of that discussion</summary> <fremy> Topic: Adding an infinity keyword<br> <RossenTheReal> github, https://github.com/w3c/csswg-drafts/issues/4688<br> <RossenTheReal> github-issue, https://github.com/w3c/csswg-drafts/issues/4688<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/4688<br> <fremy> TabAtkins: now that we have a precedent for "e" and "pi"<br> <fremy> ... heycam mentioned it could be useful to add "infinity"<br> <fremy> ... it's not useful per se, but it would allow us to serialize infinite values coming from TypedOM<br> <fremy> ... instead of 1/0<br> <fremy> TabAtkins: Anyone has opinions on this?<br> <dbaron> Tab also mentions 1px/0 and the newer option infinity*1px<br> <fremy> oriol: could we add "NaN" too?<br> <fremy> TabAtkins: do we need NaN to serialize to infinity<br> <fremy> oriol: we currently we would need to serialize as 0/0 which is strange<br> <fremy> TabAtkins: I don't think we have to serialize these values at will, only when we have that as the result of a computation<br> <jensimmons> `grid-template-column: 1fr 1fr calc(infinity);` ??????<br> <fremy> TabAtkins: and we could say that NaN as a result of a computation is an infinity<br> <TabAtkins> s/could/already/<br> <fremy> heycam: Nothing to add, but yeah I find the current serialization annoying, and since we have this concept of values now, I'd like to use it<br> <fremy> TabAtkins: Just realized TypedOM allows injecting NaN anywhere, so we might actually need to serialize NaN anywhere<br> <fremy> TabAtkins: I'm then in favor of adding NaN as a keyword<br> <jensimmons> `margin-left: calc(-1*infinity);` ???????<br> <leaverou> transitions to infinity would be ...interesting<br> <fremy> TabAtkins: (if we add any of them)<br> <fremy> TabAtkins: to answer to leaverou, we can already do that, we just would need to write as a calc() right now<br> <fremy> dbaron: Serialization would be lower case?<br> <fremy> TabAtkins: yeah, I'd serialize lowercase<br> <fantasai> s/I'd/CSS would/<br> <fremy> TabAtkins: but we could do either way, no strong opinion<br> <fantasai> s/lowercase/lowercase by default/<br> <fremy> jensimmons: what capabilities are we adding by allowing these keywords?<br> <chris> z-index: -infinity<br> <fremy> TabAtkins: none, you can already get those results today by doing computations<br> <fremy> TabAtkins: (we clamp to the maximum value if we need to)<br> <jensimmons> `margin-left: calc(-1*(1/0));` works today??<br> <fremy> TabAtkins: so, what's the room's feelings about this?<br> <TabAtkins> Yes it does<br> <astearns> it's defined, in any case<br> <fremy> chris: there are also people who want rational numbers, so outputting 1/0 as a returned value would give a bad precedent<br> <tantek_> -∞<br> <heycam> -oo<br> <fremy> chris: negative infinity would have to require a space, correct?<br> <chris> RESOLVED: no non-ASCII in Core CSS<br> <fremy> TabAtkins: yes, we would need to be careful, like usual for math in css<br> <fantasai> heycam++<br> <fremy> (the room seems to have too much fun)<br> <fremy> TabAtkins: since nobody objected, let's resolve to add them<br> <jfkthame> heycam, you need some negative letter-spacing there<br> <tantek_> could you list then explicitly in IRC?<br> <fremy> RESOLVED: add infinity and nan as new css math constants<br> <tantek_> I thought I heard NaN or nand?<br> <TabAtkins> calc(infinity), calc(-infinity), and calc(nan)<br> <chris> -moz-infinity<br> <fremy> myles: -infinity sounds odd<br> <myles> calc(negative-infinity)<br> <tantek_> -infinity-infinity<br> <jensimmons> calc(-1*infinity)<br> <fremy> TabAtkins: idents can start with dash<br> <tantek_> == 0?<br> <fremy> dbaron: but usually it's for vendor prefixes<br> <fremy> TabAtkins: (missed)<br> <fremy> RossenTheReal: let's move on<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4688#issuecomment-577134942 using your GitHub account
Received on Wednesday, 22 January 2020 11:18:50 UTC