- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 17 Aug 2017 18:30:16 +0000
- To: public-houdini-archive@w3.org
Thru a separate mechanism? `FontFace` already exists, we just need to pipe those to Custom Paint. My point tho is that `FontFace` is *not* a representation of the value of the `font` property; it's the *result* of applying the `font` query to the UA's set of available fonts. (In other words, running [FontFaceSet.load()](https://drafts.csswg.org/css-font-loading/#font-face-set-load).) This is very different from `<image>` values, which *do* directly represent a distinct resource. Chatting with @bfgeek after posting this yesterday led us to the vague idea of just providing the equivalent of `FontFaceSet.load()` to the appropriate worklets, and automagically hooking up the invalidation logic to the load status of the associated fonts when you depend on a `<font>`-typed property. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/405#issuecomment-323156250 using your GitHub account
Received on Thursday, 17 August 2017 18:30:19 UTC