- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Oct 2021 16:46:40 +0000
- To: public-css-archive@w3.org
> If it causes old browsers to drop the entire declaration as invalid, authors should simply provide two font-family declarations: first, one for old browsers using only the existing syntax, and then override it with a new-syntax version for browsers that understand it. That will work for new generics that are only available with the new syntax, but there is no incentive for content creators to use the new syntax for the existing generics. Which may be fine. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6770#issuecomment-954021241 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 28 October 2021 16:46:42 UTC