For some context, for `font-display:optional`, when the web font is already cached, Chrome (80.0.3987.7) in some cases may synchronously resolve the network request during style recalc and use it immediately for rendering. This is what I observed after reloading the test case (https://static-misc.glitch.me/optional-font-load/) for a few times. This sounds like the desired behavior, and I'd love to see it enforced by the spec. -- GitHub Notification of comment by xiaochengh Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4108#issuecomment-566282826 using your GitHub accountReceived on Monday, 16 December 2019 22:49:24 UTC
This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:57 UTC