Re: [spec-reviews] CSS font-display (#71)

> the introduction should be marked as non-normative

Happy to do so, but that's generally true.  Maybe I can just put it into the CSSWG boilerplate.

> it'd be great to see an explainer for this (and have it linked from the spec)
> there aren't meaningful examples (perhaps these could be in an explainer)

Yeah, definitely need to add some good examples.

> are the values of this property available to script? On assume so via the CSS OM, but it'd be nice to see example code.

Yes, via the CSSOM, same way all other `@font-face` descriptors are.

> how does this integrate with the CSS loader API? Does one layer on top of the other?

What's the "CSS loader API"? Do you mean <https://drafts.csswg.org/css-font-loading/>?  If so, it's kinda close to being sugar on that, but there are several specific things that aren't provided right now that mean you can't faithfully polyfill it:

* no way to be notified that the UA is requesting a font-face so it can render with it
* requires mutating styles to tell the browser "use this other font for now, while I load"
* no way to produce an "invisible fallback font face" from another arbitrary font face (particularly since it might be a system font), at least without setting `color: transparent` on the element and hoping nothing is relying on `currentcolor` doing something useful.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/spec-reviews/issues/71#issuecomment-140488131