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

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

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Fri, 29 Sep 2017 00:32:41 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-332999350-1506645149-sysbot+gh@w3.org>
> Is this a fair restatement of the issue?

Yes, this is excatly what I meant.

In addition, I'll also note that similar things can happen even if the author only specifies "FontA", in several different scenario:

* Similarly to what you said above, FontA is available on one system but not the other. On the other, instead of FontB, you get some default system font. Otherwise the logic is the same.

* "FontA" is a webfont defined through an `@font-face`, and there's some network connectivity issue of some sort, and FontA doesn't get downloaded, so you get some default system font instead, and get the double spacing vs not double spacing problem without even having to change browser.

* The font metrics of "FontA" are computed differently by different browsers. For an example, see this font I was using in line-height tests: https://github.com/frivoal/web-platform-tests/blob/line-height-experiments/css/css-line-height/support/Revalia.woff Chrome gives this font a significantly taller line-height than firefox does. So for this font, if an author developped the page on firefox and picked a size that worked fine there, you could get double spacing everywhere in Chrome despite using the same font.

GitHub Notification of comment by frivoal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/938#issuecomment-332999350 using your GitHub account
Received on Friday, 29 September 2017 00:32:33 UTC

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