- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 19 Jul 2018 21:16:40 +0000
- To: public-css-archive@w3.org
> I guess another thing that I'm wondering about is the intended scope of these definitions. For instance, that spec contains two references to `<family-name>`: That's a spec bug, yes. The one for the `font-family` property isn't marked up quite right, so it's not registering as a "type" definition (just a "value" definition); if it was, it would have already shown up as a fatal error due to duplicate definitions. > OK. FWIW, we created a list of "missing" rules Nice. You can just drop that into a single issue and tag all the specs that are mentioned. > I guess the use cases that we had in mind for regexes were: Yeah, I value machine-readability here *much* less than I value an understandable and readable grammar definition. ^_^ The prose definitions are much more acceptable, imo, as a definition for these things, and the number of times we'd actually want to do some sophisticated matching on token representations are so small in the first place. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2921#issuecomment-406417129 using your GitHub account
Received on Thursday, 19 July 2018 21:16:46 UTC