- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 Jan 2020 08:26:39 +0000
- To: public-css-archive@w3.org
> A user agent may choose to slightly delay rendering an element This seems to suggest that subsequent elements may still render. We currently define **font block period** to mean 'layout the text using the fallback font but don't render glyphs'. We need another thing that defines what browsers currently do when loading installed fonts. Is it a total render block? Will it block text selection too? I'm assuming so. I'll refer to this as **render block period**. Then, the 'block', 'swap' and 'fallback' strategies will have a small **render block period**, in addition to their **font block period**. The 'optional' strategy will just have a **render block period**. The tricky part is picking a number for the block time. UAs could even have a longer **render block period** before page load, where there's a lot of jank happening anyway. UAs could skip the **render block period** if the browser is pretty sure the period limit would be reached (eg, font is not cached, and no service worker, and network looks slow). -- GitHub Notification of comment by jakearchibald Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4108#issuecomment-572926635 using your GitHub account
Received on Friday, 10 January 2020 08:26:41 UTC