Closed
Bug 1151993
Opened 9 years ago
Closed 9 years ago
apply shrink-wrapping to orthogonal block frames
Categories
(Core :: Layout: Block and Inline, defect)
Core
Layout: Block and Inline
Tracking
()
RESOLVED
FIXED
mozilla40
Tracking | Status | |
---|---|---|
firefox40 | --- | fixed |
People
(Reporter: jfkthame, Assigned: jfkthame)
References
(Blocks 1 open bug)
Details
Attachments
(4 files)
1.35 KB,
text/html
|
Details | |
1.80 KB,
patch
|
smontagu
:
review+
|
Details | Diff | Splinter Review |
5.41 KB,
patch
|
smontagu
:
review+
|
Details | Diff | Splinter Review |
952 bytes,
patch
|
smontagu
:
review+
|
Details | Diff | Splinter Review |
See attached testcase. For the vertical <div> between the two horizontal paragraphs, we use the height of the outer containing <div> as its available isize, which is a good start. But when it contains only a small amount of text (right-hand example) we should shrink-wrap it instead of maintaining the containing block's height as a fixed inline-size for the orthogonal block. (This is what webkit/blink does.)
Assignee | ||
Comment 1•9 years ago
|
||
This seems to make the example behave as desired.
Attachment #8589242 -
Flags: review?(smontagu)
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → jfkthame
Status: NEW → ASSIGNED
Does this match what the spec says to do?
Flags: needinfo?(jfkthame)
Assignee | ||
Comment 3•9 years ago
|
||
(In reply to David Baron [:dbaron] ⏰UTC-7 from comment #2) > Does this match what the spec says to do? I think so, as best I can understand it. In particular, "If a box establishing an orthogonal flow is a block container ... for the case where the box’s inline size is auto: ... if the content neither line-wraps nor fragments ... the used inline size is the max-content inline size of the box’s contents".[1] Which I take to mean that the used height of the "Hello World" block in the example here is simply the length of the "Hello World" text. [1] http://dev.w3.org/csswg/css-writing-modes/#auto-multicol
Flags: needinfo?(jfkthame)
Assignee | ||
Comment 4•9 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=e6058eb085f1
Assignee | ||
Comment 5•9 years ago
|
||
Attachment #8589332 -
Flags: review?(smontagu)
Assignee | ||
Comment 6•9 years ago
|
||
Turns out the patch here causes an existing test to fail, but in this case that's OK: the corrected behavior makes far more sense, and we should just fix the reference file to reflect the new reality.
Attachment #8589496 -
Flags: review?(smontagu)
Updated•9 years ago
|
Attachment #8589242 -
Flags: review?(smontagu) → review+
Updated•9 years ago
|
Attachment #8589332 -
Flags: review?(smontagu) → review+
Updated•9 years ago
|
Attachment #8589496 -
Flags: review?(smontagu) → review+
Assignee | ||
Comment 7•9 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/36026abf6c53 https://hg.mozilla.org/integration/mozilla-inbound/rev/314f615d272b https://hg.mozilla.org/integration/mozilla-inbound/rev/27220470506a
Assignee | ||
Comment 8•9 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/52e5ad1e8863
Assignee | ||
Updated•9 years ago
|
Blocks: enable-writing-mode-release
Comment 9•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/36026abf6c53 https://hg.mozilla.org/mozilla-central/rev/314f615d272b https://hg.mozilla.org/mozilla-central/rev/27220470506a https://hg.mozilla.org/mozilla-central/rev/52e5ad1e8863
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
status-firefox40:
--- → fixed
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → mozilla40
You need to log in
before you can comment on or make changes to this bug.
Description
•