Skip to content

Issues: w3c/IFT

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

20 Open 85 Closed
20 Open 85 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Patch type combinations -- normative vs non-normative guidance
#240 opened Nov 19, 2024 by skef
8
Alternative high-level breakdown of patch extension algorithm
#239 opened Nov 19, 2024 by skef
Potential invalidating patch criterion for extension algorithm
#235 opened Nov 8, 2024 by skef
16
Clear up "encoding" vs "format"
#234 opened Nov 8, 2024 by skef
1
@garretrieger
1
Grouping of patches during extension
#233 opened Nov 8, 2024 by skef
@garretrieger
3
Performance of unified extension algorithm for "no invalidation" patches
#232 opened Nov 8, 2024 by skef
2
Extension algorithm language and pre-loading
#231 opened Nov 8, 2024 by skef
1
Discontinue the "Incremental Font Transfer via Range Request" specification Range Request Solution includes something specific to range-request method
#230 opened Nov 7, 2024 by svgeesus
@svgeesus
Explainer currently relies on the reader knowing about the previous IFT methods (PatchSubet/Range Request)
#225 opened Oct 29, 2024 by garretrieger
@svgeesus
Add concrete examples to the application of a patch section
#216 opened Sep 24, 2024 by rsheeter
1
Review feedback wrt making spec more readable
#213 opened Sep 24, 2024 by rsheeter
@svgeesus @garretrieger
Add @supports example to IFT spec
#212 opened Sep 24, 2024 by svgeesus
@svgeesus
Considerations for "desiccated" initial font files
#201 opened Aug 13, 2024 by skef
3
Security self-review answers for 9 July 2024 WD of IFT Priority: Eventually Long-term issue, not outside SLO privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. security-tracker Group bringing to attention of security, or tracked by the security Group but not needing response.
#194 opened Jul 24, 2024 by svgeesus
Wide Review of 9 July WD of IFT Priority: Eventually Long-term issue, not outside SLO
#193 opened Jul 24, 2024 by svgeesus
2 of 7 tasks
@svgeesus
13
Possible "all other codepoints" semantic?
#192 opened Jul 23, 2024 by skef
5
Client conformance tests help wanted Extra attention is needed Priority: Eventually Long-term issue, not outside SLO
#125 opened Sep 28, 2022 by garretrieger
@garretrieger
It'd be interesting to discuss markup discoverability
#109 opened Jul 8, 2022 by yoavweiss
2
A-la-carte IFT
#103 opened Jun 28, 2022 by skef
5
Shared Brotli ID is expired question Further information is requested
#101 opened Jun 21, 2022 by svgeesus
8
ProTip! Add no:assignee to see everything that’s not assigned.