Closed Bug 41412 Opened 21 years ago Closed 11 years ago
[FLOAT] text overlapping top edge of pushed-down float
Steps to reproduce: 1. Launch Mozilla. 2. Navigate to the following attachment. Actual result: Fourth line of the text overlap with the right floater. Expected result: text should not overlap with floats. Observed on: 2000060220 nightly build on Windows 2000.
Reassiging to Kevin for bug triage.
Assignee: clayton → kmcclusk
Steve, could you look at this? Unless clip is set on views for the floaters they will display their contents.
Assignee: kmcclusk → buster
(This bug will probably reappear once Steve checks in his float percentage width fix today (the testcase depends on that bug being fixed.) This looks bad. Nominating nsbeta3 because it's a standards-compliance issue, and it probably will affect some real web pages (especially as more pages start using CSS floats for layout).
As per meeting with ChrisD today, taking QA.
QA Contact: petersen → py8ieh=bugzilla
David: The first testcase demonstrates a bug in the quirks mode "don't push floats down" code that causes overlaps, so you are probably correct; we should disable that quirk as much as possible. The new testcase gets around this problem and demonstrates the issue very well. Note that this bug shows up on a WaSP test page. (However, this is probably one of our less dramatic float errors...)
Denied beta3: too many float bugs to fix them all for beta3
Whiteboard: hit during nsbeta2 standards compliance testing → hit during nsbeta2 standards compliance testing [nsbeta3-]
Target Milestone: --- → Future
This will make lots of pages look bad, and it makes it unsafe to use floats around text, which is the main use of floats.
I know we still do not have enough resources to get this fixed. However: Removing [nsbeta3-] to put this floater bug (and 3 others) back onto the developer radar, as per suggestion by Gerardo.
Whiteboard: [nsbeta3-] hit during nsbeta2 standards compliance testing → (beta3 minus per triaging) hit during nsbeta2 standards compliance testing
changed (beta3 minus per triaging) to [nsbeta3-] so searches work correctly
Status: NEW → ASSIGNED
Whiteboard: (beta3 minus per triaging) hit during nsbeta2 standards compliance testing → [beta3-] hit during nsbeta2 standards compliance testing
Whiteboard: [beta3-] hit during nsbeta2 standards compliance testing → [beta3-] relnote-devel hit during nsbeta2 standards compliance testing
This may be a duplicate of bug 25888.
*** Bug 59811 has been marked as a duplicate of this bug. ***
Build reassigning Buster's bugs to Marc.
Assignee: buster → attinasi
Status: ASSIGNED → NEW
It would be nice to fix this, but for Mozilla 1.0 we are already way overloaded just with crashers and dataloss bugs.
Status: NEW → ASSIGNED
Whiteboard: [Hixie-P2] (high profile: css1 test suite) relnote-devel → [CSS1-5.5.25][Hixie-P2] (high profile: css1 test suite) relnote-devel
Confirmed using FizzillaCFM/2002070913. Setting Platform=All.
Hardware: PC → All
Marking dependency on bug 25888, but not duplicate, since this is a more complicated variant of the problem that might not be fixed by any fix to bug 25888 (although it should be fixed by the *right* fix).
Depends on: 25888
bug 260095 is a duplicate of this bug. Can someone please mark it as such?
*** Bug 260095 has been marked as a duplicate of this bug. ***
*** Bug 251139 has been marked as a duplicate of this bug. ***
Another example that demonstrates the same problem but in little different situation.
*** Bug 305169 has been marked as a duplicate of this bug. ***
*** Bug 347859 has been marked as a duplicate of this bug. ***
WFM with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 and Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a1pre) Gecko/20100128 Minefield/3.7a1pre
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Yes, this was fixed by the parts of bug 25888 that landed, in particular by http://hg.mozilla.org/mozilla-central/rev/be75e40365ce .
Assignee: nobody → dbaron
Resolution: WORKSFORME → FIXED
Target Milestone: Future → mozilla1.9.2a1
You need to log in before you can comment on or make changes to this bug.