Bug 96841 - Vertical writing mode block ignores horizontal children when calculating height
Summary: Vertical writing mode block ignores horizontal children when calculating height
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 46123 96557
  Show dependency treegraph
 
Reported: 2012-09-14 16:51 PDT by John Mellor
Modified: 2017-07-18 08:30 PDT (History)
4 users (show)

See Also:


Attachments
Testcase (550 bytes, text/html)
2012-09-14 16:51 PDT, John Mellor
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description John Mellor 2012-09-14 16:51:22 PDT
Created attachment 164250 [details]
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.
Comment 1 John Mellor 2012-09-14 16:53:04 PDT
Possibly related to bug 47238?
Comment 2 Dave Hyatt 2013-03-07 15:02:49 PST
(In reply to comment #1)
> Possibly related to bug 47238?

Yes, that's the issue. We have no way of knowing how to compute min-content and max-content when they depend on a child's extent. As far as I can tell, no spec really indicates what to do yet.