- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Aug 2017 12:36:09 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `font-synthesis, again (though a bunch of it was in the previous topic)`, and agreed to the following resolutions:
* `RESOLVED: make default values: weight (off), style (off), small-caps (on), make the initial value 'weight style', and add keywords no-weight, no-style, and no-small-caps.`
<details><summary>The full IRC log of that discussion</summary>
<dbaron> Topic: font-synthesis, again (though a bunch of it was in the previous topic)<br>
<fremy> fantasai: but if we accept to break stuff, we can do default=initial, which makes more sense<br>
<dbaron> github: https://github.com/w3c/csswg-drafts/issues/1641<br>
<fremy> alan: seems like we want a new issue, and try to come up with a new design for this, and discuss this in a smaller group<br>
<fremy> alan: then come back to this when the key people for this issue agree all together<br>
<fremy> fantasai: it is a breaking change, so we want to do it sooner rather than later<br>
<fremy> alan: what is the proposal then?<br>
<fremy> dbaron: intial = default<br>
<fremy> TabAtkins: "font-synthesis: weight" also turns on "italic"<br>
<fremy> TabAtkins: that is confusing<br>
<fremy> myles_: we could three set of keywords<br>
<TabAtkins> none | [ weight || style ] | [ [weight-on | weight-off] || [style-on | style-off] || [smallcaps-on | smallcaps-off] ... ]<br>
<fremy> Florian: or we can also use the inheritance behavior<br>
<fremy> Florian: the only case that would be broken would be font-synthesis:initial<br>
<fremy> myles_: probably not common<br>
<fremy> dbaron: with this in mind, maybe i am fine with the previous resolution<br>
<fremy> dbaron: if we need to do something weird anyway, we might as well do what we proposed before<br>
<fremy> dbaron: but keep this as exceptions only for weight and style, and going forward we do default=initial<br>
<fremy> alan: so we have three proposals<br>
<fremy> 1. previous resolution<br>
<fremy> 2. extended keyword set<br>
<fremy> 3. inheritance for omitted values<br>
<fremy> fantasai: 3 would break the meaning for font-synthesis:weight<br>
<fremy> TabAtkins: no, it would not<br>
<fremy> Florian: we change the initial to no<br>
<fremy> Florian: but the ua stylesheet sets to true on root<br>
<fremy> alan: what about small-caps?<br>
<fremy> myles_: small caps is on by default<br>
<Bert> (Idea: Disallow mixing positive and negative keywords. E.g., assume initial value is 'a b d' and you set 'a c', then only a and c are on. If you set 'no-a no-c' then b and are on, i.e., the initial value minus the ones that were turned off.)<br>
<fremy> myles_: so font-synthesis:weight allows small-caps<br>
<fremy> alan: do you have a preference, myles?<br>
<fremy> myles_: not really<br>
<fremy> myles_: the ua stylesheet case is the most simple and elegant solution, probably<br>
<fremy> TabAtkins: I like florian proposal<br>
<fremy> dino: the only issue is we break all:initial, which people do in shadow dom<br>
<fremy> TabAtkins: yes, true<br>
<fremy> fantasai: if we were doing this from scratch, we would have dbaron's behavior<br>
<TabAtkins> Florian's proposal: initial value is `font-synthesis: no-weight no-style smallcaps`, UA style is `:root { font-syntheses: weight style smallcaps;}`. Omitting a keyword defaults it to the initial value for that keyword.<br>
<fremy> fantasai: how about we break existing content?<br>
<TabAtkins> So author saying `f-s: weight;` would get weight & smallcaps syntheses, but not style.<br>
<fremy> myles_: places that use it today would then never synthetize small caps<br>
<fremy> myles_: i prefer the alternative<br>
<fantasai> fremy: Why would you do 'all: initial' and not 'all: unset'?<br>
<fremy> alan: we reached the time limit<br>
<fremy> alan: i would want to come to a conclusion<br>
<fremy> dbaron: two proposals: fixing previous resolution, or breaking existing content<br>
<Bert> (idea2: use Chris's +/-. If you use a + or -, then the rule becomes "additive" :-) (relative to the initial value. 'font-synth: +weight' does not turn style off.)<br>
<dbaron> Proposed resolution: make default values: weight (off), style (off), small-caps (on), make the initial value 'weight style', and add keywords no-weight, no-style, and no-small-caps.<br>
<dbaron> More breaking option: make default values: weight (on), style (on), and small-caps (on), make the initial value 'new keyword to be determined', and add keywords no-weight, no-style, and no-small-caps<br>
<dbaron> (although there's actually the alternative option to not have the non-default no-* variants)<br>
<dbaron> (that alternative applies to both options)<br>
<fremy> alan: we try to resolve on the the first one dbaron proposed<br>
<fremy> (no objection)<br>
<fremy> RESOLVED: make default values: weight (off), style (off), small-caps (on), make the initial value 'weight style', and add keywords no-weight, no-style, and no-small-caps.<br>
<dbaron> (at least for now, may discuss further)<br>
</details>
--
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1641#issuecomment-319956404 using your GitHub account
Received on Thursday, 3 August 2017 12:36:09 UTC