dlaliberte / standards-notes Goto Github PK

Hey Daniel!

A few random comments about the explainer:

• For Font Features, I'd just say they are "Client Hints" and not "User Agent Client Hints"
• I don't think that font features should be used as critical client hints in most cases:
  • When the CSS is external, it's the CSS that you want to receive the hint, not the HTML
  • When the CSS is inlined, there's some room to consider declaring the hints as critical, but the cost of an initial RTT may outweigh the cost of sending a slightly less optimal font, so the criticallity of the fonts seems like something that should be pending on e.g. ACCEPT_CH frame support at the protocol level.
• Why are prefers-color-scheme and prefers-reduced-motion likely to impact font resources? Also, prefers-color-scheme is shipped in Chromium as a CH
• "The two major kinds of negative impacts involve the initial delay in rendering while waiting for required font files to be downloaded, and the subsequent redraws that might result when font changes require changes to page layout." - that sentence feels out of place, and also those are 2 problems that won't be fully addressed by your proposal (even if they can be improved)
• "responsive images" seem unrelated to fonts
• UA knowledge that's based on the UA's significant version is not going away, and there's no particular need to create hints for (e.g. stale-while-revalidate, unicode-range and preconnect support, that you mention)

Cheers :)
Yoav