こんにちは TAG-さん!

I'm requesting a TAG review of [Incremental Font Transfer: Patch Subset.

Incremental transfer allows clients to load only the portions of the font they actually need, which speeds up font loads and reduces data transfer needed to load the fonts.

• Explainer¹ (minimally containing user needs and example code): Explainer
• Specification URL: https://www.w3.org/TR/2023/WD-IFT-20230530/
• Tests:
  • https://github.com/w3c/ift-server-tests
  • https://github.com/w3c/IFT/issues/125
• User research: https://www.w3.org/TR/PFE-evaluation/
• Security and Privacy self-review²: https://github.com/w3c/IFT/issues/35
• GitHub repo (if you prefer feedback filed there): https://github.com/w3c/IFT
• Primary contacts (and their relationship to the specification):
  • Chris Lilley @svgeesus (W3C, editor, staff contact)
  • Myles C. Maxfield @litherum (Apple, editor)
  • Garret Rieger @garretrieger (Google, editor, co-chair)
  • Vladimir Levantovsky @vlevantovsky (W3C Invited Experts, co-chair
• Organization(s)/project(s) driving the specification: W3C WebFonts WG
• External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): not yet

Further details:

• I have reviewed the TAG's Web Platform Design Principles
• Relevant time constraints or deadlines: no rush, hope to move to CR within 6 months
• The group where the work on this specification is currently being done: W3C WebFonts WG
• Major unresolved issues with or opposition to this specification: open issues
• This work is being funded by:

You should also know that...

The Range Request method has more open issues and has been split off into a separate specification. It is not part of this TAG review request.

We are tracking Early wide review of IFT

We'd prefer the TAG provide feedback as (please delete all but the desired option):

🐛 open issues in our GitHub repo for each point of feedback