Closed
Bug 5277
Opened 26 years ago
Closed 25 years ago
[FLOAT] Floats with different parents are overlapping
Categories
(Core :: Layout, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
Future
People
(Reporter: dbaron, Assigned: buster)
References
()
Details
(Keywords: css1, Whiteboard: [nsbeta2-][nsbeta3-][rtm-] probably not hit during nsbeta2 standards compliance testing)
With a maximized window, I see overlapping floats in: Test 1 of the above URL, right side, image float (orange) on top of text float (gray). This *may* be related to the fix for weird behavior in bug 1605 on http://www.w3.org/Style/CSS/Test/current/sec5525b.htm which is now correct. I put what I am seeing (which is correct!) at: http://www.fas.harvard.edu/~dbaron/tests/nglayout/5525b_correct The difference results from the 4th line of text in the 3rd paragraph within the table. The position of those images is very strange because of the combination of overlap and negative margins, so the behavior should be different at different window sizes, but what is shown there covers the two alternatives. (Note that the difference is that within the table, the *outer* top (with negative margin) of the second float is below the first float, whereas the first time it is not.) You should watch that page for regressions if you work on this bug, I think.
Updated•26 years ago
|
Summary: Floats with different parents are overlapping → {css1} Floats with different parents are overlapping
Updated•26 years ago
|
QA Contact: 4144 → 4110
With current builds (at least with my current tree), the floaters do not overlap each other. However, the text in many of the test cases do overlap the floaters. I assume that this is bad and needs to be fixed.
Reporter | ||
Comment 2•26 years ago
|
||
Assumtion correct. However, I'm still seeing the overlap too.
Fixing this bug is too dangerous to fix in the beta; moving to just past the beta.
Reporter | ||
Comment 6•25 years ago
|
||
I think this is mostly fixed, except for one really minor problem: the text "This is short" is incorrectly indented within the table.
Why are you re-reassing layout bugs? Do NOT touch layout bugs. The bugs are assigned to Kipp so they can stay neatly organized until we have a new owner for the block/inline code.
Summary: {css1} Floats with different parents are overlapping → {css1} [FLOAT] Floats with different parents are overlapping
Comment 9•25 years ago
|
||
Migrating from {css1} to css1 keyword. The {css1}, {css2}, {css3} and {css-moz} radars should now be considered deprecated in favour of keywords. I am *really* sorry about the spam...
Comment 10•25 years ago
|
||
Is this bug still a problem? I can't see any using the 1/21 build.
Updated•25 years ago
|
Summary: {css1} [FLOAT] Floats with different parents are overlapping → [FLOAT] Floats with different parents are overlapping
Reporter | ||
Comment 12•25 years ago
|
||
I think this bug is fixed too...
Assignee | ||
Comment 13•25 years ago
|
||
Important to fix, but low priority for beta2. Moving to M17.
Status: NEW → ASSIGNED
Target Milestone: M16 → M17
Comment 14•25 years ago
|
||
Nominating nsbeta2,nsbeta3,rtm. Recc. nsbeta2+, falling through to nsbeta3+ and rtm+ if necessary. This is a W3C CSS1 Official Test Suite compliance bug.
Comment 15•25 years ago
|
||
Sorry, to clarify: this is not an nsbeta2 stopper, but I'd permit checking in prior to nsbeta2 if we have a fix. Recc. nsbeta2+[some lenient date-], falling through to nsbeta3+ hard stop if not fixed during nsbeta2. This is a W3C CSS1 Official Test Suite compliance bug.
Comment 16•25 years ago
|
||
Putting on [nsbeta2-] radar. Not critical to beta2.
Whiteboard: [nsbeta2-]
Comment 17•25 years ago
|
||
As per meeting with ChrisD today, taking QA.
Keywords: correctness
QA Contact: chrisd → py8ieh=bugzilla
Updated•25 years ago
|
Whiteboard: [nsbeta2-] → [nsbeta2-] hit during nsbeta2 standards compliance testing
Comment 18•25 years ago
|
||
Denying for beta3: bigger problems to solve in very limited time - sorry.
Whiteboard: [nsbeta2-] hit during nsbeta2 standards compliance testing → [nsbeta2-] [nsbeta3-] hit during nsbeta2 standards compliance testing
Comment 19•25 years ago
|
||
David: I'm having difficulty working out what the problem is here. Could you clarify your bug report? It doesn't help that the W3C test suite is triggering quirks mode...
Assignee: buster → dbaron
Severity: normal → minor
Status: ASSIGNED → NEW
Target Milestone: M17 → Future
Comment 20•25 years ago
|
||
(...I just realised that I must have understood this bug at some point, since I thought I had run into it. Ahem.)
Keywords: qawanted
Whiteboard: [nsbeta2-] [nsbeta3-] hit during nsbeta2 standards compliance testing → [nsbeta2-] [nsbeta3-] hit during nsbeta2 standards compliance testing (py8ieh:reexamine)
Reporter | ||
Comment 21•25 years ago
|
||
This URL in this bug was the old version of sec414. URL changed accordingly. I still don't see the bug. Ian, if you agree, please mark FIXED.
Comment 22•25 years ago
|
||
Marking WORKSFORME. The only bug I see is the float after "This is short." is too low, but that seems difficult to me (doing it right requires a reflow of previously flowed content). And that problem is definitely [nsbeta3-]. And its another bug anyway. I'm rather confused about why I marked this bug 'hit during nsbeta2 standards compliance testing'. I must have been under the influence of the XBL team's, ah, stimulants or something.
Assignee: dbaron → buster
QA Contact: py8ieh=bugzilla → dbaron
Whiteboard: [nsbeta2-] [nsbeta3-] hit during nsbeta2 standards compliance testing (py8ieh:reexamine) → [nsbeta2-] [nsbeta3-] probably not hit during nsbeta2 standards compliance testing (py8ieh:reexamine)
Comment 23•25 years ago
|
||
Ian...did you mean to mark this worksforme? Setting to [rtm-]
Whiteboard: [nsbeta2-] [nsbeta3-] probably not hit during nsbeta2 standards compliance testing (py8ieh:reexamine) → [nsbeta2-][nsbeta3-][rtm-] probably not hit during nsbeta2 standards compliance testing (py8ieh:reexamine)
Comment 24•25 years ago
|
||
Er, yes. Geez, what is wrong with me on this bug!
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Whiteboard: [nsbeta2-][nsbeta3-][rtm-] probably not hit during nsbeta2 standards compliance testing (py8ieh:reexamine) → [nsbeta2-][nsbeta3-][rtm-] probably not hit during nsbeta2 standards compliance testing
Updated•10 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•