Closed
Bug 373566
Opened 19 years ago
Closed 19 years ago
Ascent of box-wrapped IMG is absurdly large
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
RESOLVED
INVALID
People
(Reporter: roc, Unassigned)
References
Details
Attachments
(1 file)
|
165 bytes,
text/html
|
Details |
See attached testcase. Essentially the NS_INTRINSICSIZE we pass to BoxReflow here:
http://lxr.mozilla.org/seamonkey/source/layout/generic/nsFrame.cpp#5829
gets propagated around and eventually returned as the ascent of the image. This causes bad things to happen.
Comment 1•19 years ago
|
||
what kind of "bad things"? "fix on the branch" bad things?
Flags: wanted1.8.1.x?
Flags: wanted1.8.0.x?
Flags: blocking1.9?
| Reporter | ||
Comment 2•19 years ago
|
||
Content to disappear. Probably nothing that couldn't be triggered in other ways though.
| Reporter | ||
Comment 3•19 years ago
|
||
But I think this is related to reflow branch and may not be present on branch.
Blocks: reflow-refactor
Flags: blocking1.9? → blocking1.9+
This works for me on trunk and on a right-after-reflow-branch landing build.
And I'd have thought this would have been fixed by bug 366667.
| Reporter | ||
Comment 5•19 years ago
|
||
works for me too.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Updated•18 years ago
|
Flags: wanted1.8.1.x?
Flags: wanted1.8.0.x?
You need to log in
before you can comment on or make changes to this bug.
Description
•