- From: François REMY via GitHub <sysbot+gh@w3.org>
- Date: Sat, 24 Jun 2017 17:38:36 +0000
- To: public-css-archive@w3.org
@aaaxx well, the handling of ligatures isn't wrong because font-feature-settings beats other properties <a href="https://drafts.csswg.org/css-fonts-4/#feature-variation-precedence">per the spec</a> but, you are right, if I didn't do anything, ligatures would have been disabled. You are also right the workaround isn't perfect but the question is whether it is good enough for the desired use cases. Having a background on the inlines isn't working well in that scenario. Underlines is another example of something that doesn't work well. It would be interesting to study why people use letter-spacing on actual websites. I'm wondering, because even on Google.com, it is used as a hack for various things none of them striking me as the intended purpose of letter-spacing. Given how fragile hacks usually are and how widespread their use seems to be, changing the behavior of letter-spacing now seems unrealistic to me. Another option to consider, if we decide the statu quo isn't good enough, would be to add a new property altogether. I would prefer to adding a flag for letter-spacing. We could repurpose letter-spacing to be exactly the behavior websites depend on today, then add glyph-spacing to behave as we wish letter-spacing should have worked. -- GitHub Notification of comment by FremyCompany Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1518#issuecomment-310852931 using your GitHub account
Received on Saturday, 24 June 2017 17:38:42 UTC