Open
Bug 1344638
Opened 9 years ago
Updated 4 years ago
The behaviors of text-top / text-bottom are different to Blink and Edge when line-height is not 1.
Categories
(Core :: Layout: Block and Inline, defect)
Core
Layout: Block and Inline
Tracking
()
UNCONFIRMED
People
(Reporter: tommykuo, Unassigned)
Details
Attachments
(2 files)
I found the result of the following case rendered by Gecko is different to the one rendered by Blink.
https://jsfiddle.net/Lbgeo8ab/7/
| Reporter | ||
Comment 1•9 years ago
|
||
I also tested on Edge, the behavior is also different to Gecko. But it's same with Blink.
Comment 2•9 years ago
|
||
I don't see difference between Gecko and Blink on Windows from your testcase. Could you provide a screenshot to show what you're seeing?
Comment 3•9 years ago
|
||
Also no differences between Firefox and Chrome here on Windows 8.1 (except some anti-aliasing). See attached screenshot.
| Reporter | ||
Comment 4•9 years ago
|
||
This screenshot is the difference what I see.
| Reporter | ||
Comment 5•9 years ago
|
||
I found the difference is caused by the font. After install the font[1], I found the different behavior happens when the line-height is not 1. I'll attach the screenshot later.
[1]: https://github.com/w3c/web-platform-tests/tree/master/css/fonts/ahem
Summary: The behaviors of text-top / text-bottom are different to Blink and Edge. → The behaviors of text-top / text-bottom are different to Blink and Edge when line-height is not 1.
| Reporter | ||
Comment 6•9 years ago
|
||
Oh, I know what the problem is. `line-height: normal` equals to `line-height: 1` on Chrome. But it's 1.2[1] in Firefox.
[1]: https://developer.mozilla.org/en/docs/Web/CSS/line-height
Status: NEW → UNCONFIRMED
Ever confirmed: false
Updated•4 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•