[Webkit-unassigned] [Bug 96841] New: Vertical writing mode block ignores horizontal children when calculating height
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Sep 14 16:50:55 PDT 2012
https://bugs.webkit.org/show_bug.cgi?id=96841
Summary: Vertical writing mode block ignores horizontal
children when calculating height
Product: WebKit
Version: 528+ (Nightly build)
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: Layout and Rendering
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: johnme at chromium.org
CC: jchaffraix at webkit.org, ojan at chromium.org
Blocks: 46123
Created an attachment (id=164250)
--> (https://bugs.webkit.org/attachment.cgi?id=164250&action=review)
Testcase
When a vertical-lr block with height:auto contains a horizontal-tb child, it's computed height ends up being just the height of its child's borders, ignoring the actual content of the child.
This seems pretty broken. My reading of http://dev.w3.org/csswg/css3-writing-modes/#orthogonal-flows and http://dev.w3.org/csswg/css3-writing-modes/#orthogonal-auto is that:
- max-content is the height of .inner (the green box)*
- min-content is the height of .inner (the green box)*
- fill-available is infinite since the height of the body is auto, so is ignored
- fill-fallback is the height of the initial containing block
Hence contentHeight of .outer = min(max-content, max(min-content, fill-fallback)) = height of .inner (the green box) [including .inner's borders and padding].
*: Though it's not clear how orthogonal writing mode interacts with the definitions of min-content and max-content (http://dev.w3.org/csswg/css3-writing-modes/#min-content), where min-content supposes that "all line break opportunities within the box were taken" and max-content supposes that "none of the optional line break opportunities within the box were taken"; indeed that seems somewhat backwards in this situation.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list