Open Bug 1072762 Opened 11 years ago Updated 2 years ago

implement the FontFaceSet constructor

Categories

(Core :: CSS Parsing and Computation, defect)

defect

Tracking

()

People

(Reporter: heycam, Unassigned)

References

Details

(Keywords: dev-doc-needed)

The CSS Font Loading API allows the creation of separate FontFaceSet objects not tied to a document. We don't implement that yet (and we might want to push back on that since I'm not sure how useful it is to be honest).
Severity: normal → S3

This feature request is now a web branding problem.

Running the following snippet in the js console has different behavior in each major browser:

let f = new FontFaceSet([]);

In Safari 17.5 (macOS 14.5):

  • Returns a new FontFaceSet with no initial fonts

In Chromium 124.0.6367.207 (snap, Ubuntu 22.04):

  • ReferenceError: FontFaceSet is not defined. The interface is not exposed to JS, but the type is visible when logging document.fonts

In Firefox 125.0.2 (snap, Ubuntu 22.04):

  • TypeError: Illegal constructor.
Flags: needinfo?(erights)

Redirect a needinfo that is pending on an inactive user to the triage owner.
:emilio, since the bug has recent activity, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(erights) → needinfo?(emilio)

https://issues.chromium.org/issues/40287940 indicates that this is probably worth trying to remove from the spec.

Flags: needinfo?(emilio)
You need to log in before you can comment on or make changes to this bug.