Bug 75283 - Nested ruby rendering "collapses" when the line-height CSS property exceeds a certain value
Summary: Nested ruby rendering "collapses" when the line-height CSS property exceeds a...
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac (Intel) OS X 10.6
: P2 Major
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-27 17:34 PST by waynerj
Modified: 2024-04-09 06:38 PDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description waynerj 2011-12-27 17:34:31 PST
Overview:
Nested ruby rendering "collapses" (the top line gets rendered where the next line below it is) when the line-height CSS property exceeds a certain value.

Steps to Reproduce:
Go to http://www.chinesetools.net/ruby/Mandarin-Expressions_line-height_bug.html.

Note the difference between the nested ruby elements in the "b...(line-height: 3.2em)" paragraph and the ones in the "bu...(line-height: 3.3em)" paragraph.

Actual Results:
When the line-height is set to 3.3em or higher instead of 3.2em, the top line of a nested ruby element gets rendered in the same location as the line that is supposed to be below it, as if the 3rd floor of a building collapsed down into the 2nd floor.

Expected Results:
The nested ruby elements should maintain their integrity as line-height increases.

Build & Platform:
Version 5.1.2 (6534.52.7, r103700) on Intel Mac OS X 10.6.8
Comment 1 waynerj 2011-12-27 18:21:50 PST
On WebKit r103743 on Windows Vista, the "collapsing" occurs at line-height: 3.2em, but not at line-height: 3.1em. Evidently the threshold is slightly different on different platforms.
Comment 2 Ahmad Saleem 2024-04-08 23:07:52 PDT
I tried to find wayback archive link for the test case but it seems that it redirects to unknown site.

Due to lack of tests and recent progressions in CSS-Ruby, I think we should mark this as 'RESOLVED CONFIGURATION CHANGED', unless if it is still applicable and we have test case reflecting that it is still an issue.


@Alan - any thoughts?
Comment 3 zalan 2024-04-09 06:38:18 PDT
I wish we could close it as "insufficient information".