- From: Jonathan Kew <jfkthame@gmail.com>
- Date: Tue, 6 Aug 2019 10:44:47 +0100
- To: public-webfonts-wg@w3.org
On 05/08/2019 23:35, Garret Rieger wrote: > This will of course add some extra size to the first response, but > having the client know in advance the specific code points in the source > font has value beyond compressing the sets. For example if the browser > knows which codepoints are in the font it doesn't need to waste > requests/bytes sending augmentation requests for codepoints that aren't > actually in the font. It's pretty important for the browser to know early on which codepoints are in the font. It needs this in order to be able to appropriately fall back to the next font in the font-family list (perhaps kicking off a new font load for a different resource) for characters that aren't going to be supported by this one even after it is fully loaded. Equally, if a given character *is* going to be supported by the current font (even though it hasn't been fetched yet), we don't want the browser to start loading further fonts in the stack. JK
Received on Tuesday, 6 August 2019 09:45:13 UTC