- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 May 2019 21:33:28 +0000
- To: public-css-archive@w3.org
Yup. What people *want* to do is set which font face will be used for rendering text, and let that inherit. What they're *instead allowed* to do is set up inputs to a font-matching query that is, for each element, executed against the element's scope's set of font faces. If they set some properties expecting the font query to resolve a certain way (based on the set of @font-face rules in the outer document) so they think they can predict what their text will look like, but it then inherits into a shadow which adds more entries to the map that happen to shadow a query result (by accident, since the shadow has no easy way of querying what fonts are already available), that's an unexpected behavior change. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1995#issuecomment-495393246 using your GitHub account
Received on Thursday, 23 May 2019 21:33:31 UTC