Open
Bug 132204
Opened 23 years ago
Updated 2 years ago
nsIFrame::AddCSSMaxSize returns wrong boolean
Categories
(Core :: Layout, defect, P3)
Core
Layout
Tracking
()
NEW
People
(Reporter: bzbarsky, Unassigned)
Details
Attachments
(2 files)
654 bytes,
application/vnd.mozilla.xul+xml
|
Details | |
814 bytes,
patch
|
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
nsIBox::AddCSSMaxSize returns (widthSet || heightSet) Both nsIBox::AddCSSMinSize and nsIBox::AddCSSPrefSize return (widthSet && heightSet) and based on the code at http://lxr.mozilla.org/seamonkey/source/layout/xul/base/src/nsContainerBox.cpp#559 the MinSize/PrefSize return value seems to be correct....
Updated•15 years ago
|
QA Contact: moied → layout
Updated•15 years ago
|
Assignee: hyatt → nobody
This testcase demonstrates incorrect layout caused by this bug. Is it worth fixing though, given that the bug has existed for so long? It could potentially break content that depends on the buggy implementation.
Note that current versions of Firefox will not open the testcase by default. You'll need to do one of the following: 1. Set |dom.allow_XUL_XBL_for_file| to true, then save the testcase to disk and open it as a file, or 2. Install https://addons.mozilla.org/en-US/firefox/addon/remote-xul-manager/ and add bugzilla.mozilla.org to the remote XUL whitelist.
Summary: nsIBox::AddCSSMaxSize returns wrong boolean → nsIFrame::AddCSSMaxSize returns wrong boolean
Assignee: nobody → mjh563
Attachment #785438 -
Flags: review?(bzbarsky)
Reporter | ||
Comment 5•11 years ago
|
||
Comment on attachment 785438 [details] [diff] [review] patch r=me I guess, but I too wonder whether it's worth messing with this...
Attachment #785438 -
Flags: review?(bzbarsky) → review+
Updated•2 years ago
|
Assignee: mjh563 → nobody
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•