- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Fri, 12 Aug 2016 21:42:25 +0000
- To: public-css-archive@w3.org
According to the following test:
<!DOCTYPE html>
<meta charset=utf-8>
<style>
p { border: solid 1px black; color: silver; font-size: 100px;
line-height: 1; margin: 0.1em;}
p > * { border: 1px dotted red; }
</style>
<p style="font-family: Ahem, SimSun"><span>Ép不</span>
<p style="font-family: SimSun, Ahem"><span>Ép不</span>
<p style="font-family: Ahem, SimSun"><span>不</span>
Blink and Gecko use the metrics of the first available font to
determine the bounding box of any given inline.
Related test with multiple inlines (gives different results than font
fallback):
<p style="font-family: SimSun"><span>不A</span><span
style="font-family: Ahem">Ép</span>
I think this behavior makes sense and we should update the spec
accordingly. It has the benefit of minimizing any line-height
jitter.
“The height of the inline box encloses all glyphs and their
half-leading on each side and is thus exactly 'line-height'.”
Afaict this would mean fixing the contradiction in favor of the second
clause in this sentence, not the first.
--
GitHub Notification of comment by fantasai
Please view or discuss this issue at
https://github.com/w3c/csswg-drafts/issues/391#issuecomment-239566878
using your GitHub account
Received on Friday, 12 August 2016 21:42:32 UTC