Skip to content

Font format support (WOFF2/WOFF) #8

Description

@firejune

Tracking issue, low priority. Fonts (WOFF2/WOFF) are a natural cutting target — wOF2/wOFF signatures are constant, while the header's flavor/length/numTables fields and the table directory vary per file — but two things gate it:

  1. In real consumers fonts are typically bundle-emitted (hashed filenames), so Extend cutting to bundle-emitted assets, not just publicDir copies #7 is a prerequisite.
  2. The consumer must load fonts through the FontFace API (Blob URL) instead of CSS @font-face url(), which is a migration on their side.

One more axis to keep in mind: fonts usually carry third-party redistribution licenses, so the sensitivity of shipping them openable differs from first-party images — worth a note in the docs when this lands.

Filed so the roadmap keeps the candidate visible; no implementation planned until #7 exists.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions