- From: Mike Bremford via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 May 2020 11:32:41 +0000
- To: public-css-archive@w3.org
Ha, I'd completely forgotten about this one - didn't even recognise it as one of mine at first. I still can't see any reason why multiple families aren't allowed, and given the syntax would essentially be identical to multiple `@font-face` blocks, it's not going to break anything - it feels unlikely that someone, somewhere, is relying on a currently invalid `@font-face` with multiple families remaining invalid. But I'm struggling to see a huge benefit either, if I'm honest - I just don't know how often this comes up in the real world. If there's an l10n argument for it, I'm pretty confident I'm not the one to make it. Will leave to your discretion Chris, but if you want to close (as "Commenter Apathetic"?) I'm fine with that. -- GitHub Notification of comment by faceless2 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3691#issuecomment-622353556 using your GitHub account
Received on Friday, 1 May 2020 11:32:43 UTC