Closed
Bug 379654
Opened 16 years ago
Closed 13 years ago
spacer doesn't handle many types of width/height values
Categories
(Core :: Layout: Block and Inline, defect)
Core
Layout: Block and Inline
Tracking
()
RESOLVED
INVALID
People
(Reporter: dbaron, Unassigned)
References
Details
nsSpacerFrame, used to implement HTML spacer elements, doesn't handle many types of values for CSS 'width' and 'height' properties, and also doesn't handle min-width and max-width. See the XXX comments I'm adding to nsSpacerFrame as part of bug 311415. (Not sure if spacer really needs its own frame class. It could perhaps be block / inline-block depending on type.)
Reporter | ||
Comment 1•16 years ago
|
||
It also doesn't use the correct basis for percentage widths and heights.
Reporter | ||
Comment 2•16 years ago
|
||
(And, in fact, for percentage heights, it does math on NS_UNCONSTRAINEDSIZE.)
Reporter | ||
Comment 3•16 years ago
|
||
Though the simplest fix here is probably to just use mComputedWidth / mComputedHeight when applicable.
Comment 4•13 years ago
|
||
(In reply to comment #3) > Though the simplest fix here is probably to just use mComputedWidth / > mComputedHeight when applicable. Even simpler than that would be to remove the support for this element (bug 531030)!
Comment 5•13 years ago
|
||
spacer is dead.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•