- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Aug 2017 23:01:23 +0000
- To: public-houdini-archive@w3.org
Okay, so there are two totally different ways of talking about "font faces" that we need to address here. First is the equivalent of @font-face, representing an actual, concrete font face. This is a ResourceValue or equivalent, can be passed around to Worklets so they can use fonts, etc. I *think* this is just the already-existing [FontFace](https://drafts.csswg.org/css-font-loading/#fontface-interface) interface, and we can just use that directly. Second is representing the value of the 'font' property, which is a *search query* against the document's font faces. It's not a font face itself, it doesn't load anything, etc. This just needs to be an object with `face`, `weight`, etc fields on it, with each being CSSKeywordValues or CSSNumericValues, etc. The latter can be pushed off for now, with us just relying on CSSStyleValue to handle it, if we dont' want to handle it at the moment. For the former, is there anything wrong with just returning FontFace objects? More importantly, tho, when is this ever expected to be returned from a TypedOM API? No property will ever return this as a value; so it seems we can just ignore it too? -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/405#issuecomment-322922909 using your GitHub account
Received on Wednesday, 16 August 2017 23:01:28 UTC