- From: Mike Bremford via GitHub <sysbot+gh@w3.org>
- Date: Fri, 20 Dec 2019 12:26:54 +0000
- To: public-css-archive@w3.org
You could always add rgb(n) and rgb(n/a), which seems harmless enough, but please don't drop gray() without giving a syntax that doesn't presume RGB. We've had a colorspace called "gray" in PDF/PostScript since forever, with 0=black. It's defined as the black in CMYK - so `gray(1) == cmyk(0 0 0 1)`. I presume that's the origin of this name in CSS, but I completely agree that without this context the name is ambiguous. So while I can certainly live with gray(), if it's going to change then I'd go for black(), as it's mapped to black ink in print. -- GitHub Notification of comment by faceless2 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4621#issuecomment-567908331 using your GitHub account
Received on Friday, 20 December 2019 12:26:56 UTC