- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Aug 2018 23:49:24 +0000
- To: public-css-archive@w3.org
The Working Group just discussed `issues with font-family descriptor in @font-palette-values rule`, and agreed to the following: * `RESOLVED: Add normative text describing this issue and being more clear about how this all works with an example for how things can go terribly wrong` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: issues with font-family descriptor in @font-palette-values rule<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/1669<br> <dael> chris: I think basic problem is spec says if you say font-family it will be unique IDed. fine for fallback between diff families. Composit font there is no guar there is the same pallate with same palette values.<br> <dael> myles: Proposal to solve? I think as-is is fine and authors should make composite fonts correctly.<br> <dael> chris: Other cases where users can come up with thier own values and map with @font-face, but that's a lot of complexity. Maybe allow it to be an @font-face and define it there...not sure. Worried about too complex<br> <dael> myles: Agree. Worried about making this really complicated.<br> <dael> myles: I think there are a couple different @rules that apply to a font-family by name. If this is a problem here it's for the other like font-feature-values<br> <dael> chris: Yeah, exactly. That one too<br> <dael> myles: Another point, there can be different items in source list and you could want this specific to an item in the source list, but that's crazy. This is finding the right line in the middle<br> <dael> chris: If you do silly things you get strange results.<br> <dael> myles: That's my thought<br> <dael> astearns: Proposal is to close this no change?<br> <dael> myles: I could add normative text<br> <dael> myles: that makes it clear each of these are applied to each @font-face that share a family name. There's 2 parts and part 1 is I'm confused part 2 is is valuable. Part 2 we said no so let's describe<br> <dael> astearns: An example of how things can go wrong would be good<br> <dael> myles: Sure<br> <dael> astearns: Prop: Add normative text describing this issue and being more clear about how this all works with an example for how things can go terribly wrong<br> <fantasai> sgtm<br> <dael> astearns: Objections?<br> <dael> RESOLVED: Add normative text describing this issue and being more clear about how this all works with an example for how things can go terribly wrong<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1669#issuecomment-409760996 using your GitHub account
Received on Wednesday, 1 August 2018 23:49:33 UTC