- From: Vladimir Levantovsky via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 Mar 2021 17:46:51 +0000
- To: public-css-archive@w3.org
> Perhaps developers can be given more control to make sure which characters are fetched the first time, perhaps in a similar syntax to how Unicode ranges are given? I agree that giving developers a way to define what characters should be included / added in the incremental character set request would be useful (even though I can't come up with the clear-cut use case for it). However, from incremental font loading POV - I think this is an orthogonal issue that has no bearing on the font loading mechanism. Regardless of the approach used (a range request or a patch-subset mechanism), the incremental font load starts with a character set request. Whether the request is purely dynamic (generated by a browser based solely on the page content), or whether it combines in parts a dynamic subset and additional codepoints makes no difference on the incremental font load - when a request is made the response will be generated according to that request. Hence, IMO we should be considering an independent mechanism to inject a set of characters defined by a developer into a dynamic subset generated by a browser, before a request is made. -- GitHub Notification of comment by vlevantovsky Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6063#issuecomment-800475676 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 16 March 2021 17:46:53 UTC