Re: [csswg-drafts] [css-text] Clarify what ligatures are optional (#2644)

The CSS Working Group just discussed `Clarify what ligatures are optional`, and agreed to the following:

* `RESOLVED: Accept changes in https://github.com/w3c/csswg-drafts/commit/caf1e4747f2bd906bb9f671af8c463b28b97deda`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Clarify what ligatures are optional<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2644#issuecomment-432774658<br>
&lt;fantasai> s/no change/no shaping across positive margins, borders, pading/<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/2644#issuecomment-422075536<br>
&lt;dael> fantasai: This one I committed some changes to CSS Text to define what myles_ suggested is correct. myles_ posted ^<br>
&lt;fantasai> * rlig is required, no other ligatures are required<br>
&lt;dael> fantasai: Then text engine heuristics might apply other features<br>
&lt;fantasai> * text engines have heurstics for broken stuff, spec shouldn't override<br>
&lt;dael> fantasai: Committed that.<br>
&lt;dael> fantasai: There was discussion about needing update to font<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/commit/caf1e4747f2bd906bb9f671af8c463b28b97deda<br>
&lt;dael> fantasai: Commit for CSS 3 Text ^<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/2644#issuecomment-437085666<br>
&lt;dael> fantasai: Ccomments about changing fonts to clarify interactions. Wanted WG to discuss. Changes are largely that the section that defines how font features interact. There's a section that says [read]<br>
&lt;dael> fantasai: Should say optional ligatures as is in spec. Then clarify that if you set letter spacing later it disables all ligatures, not just common<br>
&lt;dael> fantasai: Also a suggestion there should be step 6 that says if the engine does stuff under the hood it might take precedence.<br>
&lt;dael> fantasai: I don't know about that, it's beyond my knowledge.<br>
&lt;dael> fantasai: Clarification to which ligatures are disabled should go in.<br>
&lt;dael> Rossen: What's in the PR of the 6?<br>
&lt;dael> fantasai: Changes made to text are committed. Basically clarifies optional ligature. I didn't think that text should spec what that means.<br>
&lt;dael> fantasai: Making sure text doesn't conflict with font and says go look for exact details. I think that's correct.<br>
&lt;dael> fantasai: [reads commit]<br>
&lt;dael> fantasai: I'm guessing no issues with this one. Need to figure out font spec and if there should be a step 6<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/2644#issuecomment-437085666<br>
&lt;dael> fantasai: If you look at ^ there's a list of precedence of parts of CSS that inject font feature settings.<br>
&lt;dael> fantasai: Proposal to make changes to that list<br>
&lt;dael> fantasai: Wanted to bring that up to see if we should make those changes to font. If so it should be fonts 3 as well as 4<br>
&lt;dael> Rossen: 3? Isn't that too late?<br>
&lt;dael> fantasai: Clarification to what's happening<br>
&lt;dael> Rossen: I know myles_ is reading on IRC. Hoping he'll chime in<br>
&lt;dael> Rossen: For CSS Text L3 would any additional changes be required?<br>
&lt;dael> Rossen: I know we need to take to font 3 and/or 4. What about Text 3?<br>
&lt;dael> fantasai: Nothing more. The commit went in.<br>
&lt;dael> Rossen: To close CSS Text discussion, are there any objections to proposed changes in the commit https://github.com/w3c/csswg-drafts/commit/caf1e4747f2bd906bb9f671af8c463b28b97deda ?<br>
&lt;dael> RESOLVED: Accept changes in https://github.com/w3c/csswg-drafts/commit/caf1e4747f2bd906bb9f671af8c463b28b97deda<br>
&lt;dauwhe> +1<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2644#issuecomment-444701720 using your GitHub account

Received on Thursday, 6 December 2018 00:21:20 UTC