W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2017

Re: [csswg-drafts] [css-rhythm-1] Avoiding accidental double spacing

From: Koji Ishii via GitHub <sysbot+gh@w3.org>
Date: Mon, 02 Oct 2017 19:34:11 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-333640674-1506972838-sysbot+gh@w3.org>
Thank you for your replies, it gave me a new understanding of the problem.

Is this issue suggesting to add e.g., `auto` to compute the step unit from the used line height? If that's the case, I'm ok with it, it's just not in any use cases and no one made such requests ever.

With Line Grid, as far as I talk to web developers, they normally want different line height from grid, so their usual CSS looks like:
```css
.line-grid {
  line-height: 1.4;
  -webkit-line-grid: create;
  -webkit-line-snap: contain;
}
.line-grid > * {
  line-height: 1.2 or normal or some other values;
}
```
If author uses `normal` to make the design i18n-friendly, [here is the modified example jsbin (again for Safari to view)](http://output.jsbin.com/mevuzex/). As you can see it, if the content uses taller fonts, there's a fallback that causes everything to be double-spaced.

<img width="530" alt="2017-10-03 4 07 35" src="https://user-images.githubusercontent.com/1274377/31095042-4a7af8a0-a7f2-11e7-95c9-3d680505fb62.png">

So I don't see much differences, but I understand our assumption on how authors use Line Grid is different, and if `auto` can save some English cases, I'm fine to add it.

-- 
GitHub Notification of comment by kojiishi
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/938#issuecomment-333640674 using your GitHub account
Received on Monday, 2 October 2017 19:34:01 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:19 UTC