Closed
Bug 165062
Opened 22 years ago
Closed 7 years ago
[FLOAT]IE does not wrap two consecutive floaters in a nowrap div
Categories
(Core :: Layout: Floats, defect, P3)
Core
Layout: Floats
Tracking
()
RESOLVED
INVALID
Future
People
(Reporter: alexsavulov, Unassigned)
References
()
Details
the testcase in URL shows us that two consecutive floaters can wrap in a nowrap
block. although there are no rules for floaters in nowrap blocks about that, IE
acts different.
the testcase comes from bug 78820
Reporter | ||
Updated•22 years ago
|
Priority: -- → P3
Target Milestone: --- → mozilla1.3alpha
Reporter | ||
Updated•22 years ago
|
Summary: IE does not wrap two consecutive floaters in a nowrap div → [FLOATER]IE does not wrap two consecutive floaters in a nowrap div
Updated•22 years ago
|
QA Contact: petersen → amar
Reporter | ||
Updated•22 years ago
|
Summary: [FLOATER]IE does not wrap two consecutive floaters in a nowrap div → [FLOAT]IE does not wrap two consecutive floaters in a nowrap div
There's no reason to deviate from standards at all unless major pages or
significant numbers of real pages on the web depend on IE's behavior. If that
were the case, then it would be acceptable to deviate from standards in quirks mode.
Reporter | ||
Comment 2•22 years ago
|
||
->Layout:Floats
Assignee: alexsavulov → float
Component: Layout → Layout: Floats
QA Contact: amar → ian
Target Milestone: mozilla1.3alpha → ---
Updated•22 years ago
|
Target Milestone: --- → Future
Updated•15 years ago
|
Assignee: layout.floats → nobody
QA Contact: ian → layout.floats
Comment 4•7 years ago
|
||
(I ran across this bug when searching bugzilla for bugs filed for a different float issue, and figured I'd close the loop while I'm here.)
IIUC, this bug was filed for a case where Mozilla didn't match IE (per comment 0) but did match the standards (per comment 1), on the suspicion that we might hit web compatibility issues. Apparently we didn't run into such issues, though, and our current rendering matches the now-dominant browser (Chrome)'s rendering of the linked testcase, so I think we can close this as INVALID since there's nothing to be fixed here.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•