- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Thu, 22 Apr 2021 11:54:08 +0000
- To: public-css-archive@w3.org
emilio has just created a new issue for https://github.com/w3c/csswg-drafts:
== [css-font-loading] Lack of interop on FontFace constructor. ==
```js
new FontFace("Font 01", "").family
```
Is an empty string in Gecko, because `Font 01` is not a valid family name (you need to quote it because `01` is not a CSS identifier)
Safari says `normal`.
Chrome says `Font 01`.
My understanding is that Gecko is right, per https://drafts.csswg.org/css-font-loading/#font-face-constructor:
> Parse the family argument, and the members of the descriptors argument, according to the grammars of the corresponding descriptors of the CSS @font-face rule. If the source argument is a CSSOMString, parse it according to the grammar of the CSS src descriptor of the @font-face rule. If any of them fail to parse correctly, reject font face’s [[FontStatusPromise]] with a DOMException named "SyntaxError", set font face’s corresponding attributes to the empty string, and set font face’s status attribute to "error". Otherwise, set font face’s corresponding attributes to the serialization of the parsed values.
But given the lack of interop other members may disagree? What is exactly going on in Safari / Chrome?
@litherum @lilles
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6236 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 22 April 2021 11:54:13 UTC