- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Jan 2020 21:14:34 +0000
- To: public-css-archive@w3.org
> it means the predefined ones like display-p3 don't have to become "display-p3". They wouldn't, that's the point. The predefined ones stay exactly as they are, it's the user-defined that have to do something else. > no more double hyphens They're well-established and will show up more regardless. Names in strings are the rare thing; as I said, we use them pretty much exclusively for names that come from outside CSS, and thus have no guarantees of being friendly to CSS tokenization rules (like font-face names, variation axis names, lang codes, etc.) We have no precedent for using them for things defined by the CSS author. (@font-face just works with the existing weird pattern that font-family established since CSS1; if we were doing it today it would probably instead be that all "local" fonts required strings, and all @font-face required --idents.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4654#issuecomment-572759271 using your GitHub account
Received on Thursday, 9 January 2020 21:14:36 UTC