- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Jan 2020 09:21:29 +0000
- To: public-css-archive@w3.org
@tdresser > Is there a use case for the current definition of optional that we'd lose by making this change? I still think we need to define how browsers render when they load fonts from disk. I've never seen this create layout stability issues, but maybe there are extreme cases where it does. Either way, this is the behaviour we want for `optional`, but with an aggressive timeout where it switches to a fallback. -- GitHub Notification of comment by jakearchibald Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4108#issuecomment-574080329 using your GitHub account
Received on Tuesday, 14 January 2020 09:21:30 UTC