Open
Bug 826204
Opened 13 years ago
Updated 3 years ago
nsHTMLReflowState ComputedHeight() & mComputedHeight should be compared to NS_AUTOHEIGHT, not NS_UNCONSTRAINEDSIZE
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
NEW
People
(Reporter: dholbert, Unassigned)
Details
Right now, we compare nsHTMLReflowState::ComputedHeight() (and mComputedHeight) to NS_AUTOHEIGHT in some places and to NS_UNCONSTRAINEDSIZE in other places.
Those happen to be #defined to be equal, so it doesn't actually make a functional difference which one you use. But for consistency/readability, we should stick with one or the other, as the "special value" for computed-height.
Right now, the nsHTMLReflowState.h documentation for mComputedHeight mentions NS_AUTOHEIGHT, *not* NS_UNCONSTRAINEDSIZE -- so that's probably what we should be using.
https://mxr.mozilla.org/mozilla-central/source/layout/generic/nsHTMLReflowState.h?rev=129629b6106f&mark=272-278#265
| Reporter | ||
Updated•13 years ago
|
OS: Linux → All
Hardware: x86_64 → All
Summary: nsHTMLReflowState ComputedHeight() & mComputedHeight should be compared to to NS_AUTOHEIGHT, not NS_UNCONSTRAINEDSIZE → nsHTMLReflowState ComputedHeight() & mComputedHeight should be compared to NS_AUTOHEIGHT, not NS_UNCONSTRAINEDSIZE
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•