Open
Bug 395910
Opened 17 years ago
Updated 2 years ago
Hidden children in a <deck> overlap parent's border
Categories
(Core :: Layout, defect)
Tracking
()
NEW
People
(Reporter: ecfbugzilla, Unassigned)
References
Details
(Keywords: regression, testcase)
Attachments
(2 files)
See attached testcase, we have a deck inside a box with rounded border. The visible child in the deck also has rounded border so that we don't have any overlapping - both borders are visible. However, if we add an invisible child to the deck, part of parent's border disappears, as if we had overlapping with this invisible child. I couldn't find any workaround, styles on the invisible child have no effect.
I see this in today's Minefield nightly (3.0a8pre 2007091204), Firefox 2.0.0.6 doesn't show this behavior however. I think this regressed only recently (in July or later).
Comment 1•17 years ago
|
||
I don't see anything wrong with the border here. Can you either describe what is being displayed wrong or provide a screenshot of what you see and/or expect to see?
Reporter | ||
Comment 2•17 years ago
|
||
The screenshot shows the wrong and the correct behavior (top and bottom respectively). In the trunk nightlies part of the red border is missing - something that doesn't happen if the deck doesn't have any invisible children.
Comment 3•17 years ago
|
||
OK, looks to be Windows only then.
Comment 4•17 years ago
|
||
Need to find a regression range here.
Comment 5•17 years ago
|
||
This regressed between 2007-04-30 and 2007-05-01:
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2007-04-30+04&maxdate=2007-05-01+09&cvsroot=%2Fcvsroot
I think a regression from bug 368247.
Comment 6•17 years ago
|
||
(In reply to comment #3)
> OK, looks to be Windows only then.
No, I see this on Linux as well (with a 20070909 nightly build).
Comment 7•14 years ago
|
||
WFM on Windows in 3.6.3.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•