23412 - [FLOAT] replaced block level elements flowing around floats

Status: VERIFIED DUPLICATE of bug 18445

(Core :: Layout, defect, P2)

Description

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

DESCRIPTION:  Replaced block-level elements are flowing around floats.  All
block-level elements, whether replaced or non-replaced, should be positioned as
if floats don't exist.  See the relevant section of CSS:

http://www.w3.org/TR/REC-CSS2/visuren.html#propdef-float

STEPS TO REPRODUCE:
 * load attached test case

ACTUAL RESULTS:
 * the big image is next to the four small ones at the left edge of the page,
and overflows off of the right edge of the page

EXPECTED RESULTS:
 * the big image should fit nicely within the page and should cover up the four
small images at the left.

DOES NOT WORK CORRECTLY ON:
 * Linux, mozilla, 2000-01-06-13-M13

Comment 1

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Attachment: test case described in bug

Comment 2

[troy]

Floater bug so re-assigning to Kipp's bug list

Comment 3

[buster]

mass-moving bugs to M15

Comment 4

[Hixie (not reading bugmail)]

This bug is basically the same as bug 18445, but I am not marking this as a DUP
since this bug uses images and bug 18445 uses form fields.

Comment 5

[Hixie (not reading bugmail)]

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 6

[buster]

mine! mine mine mine!  all mine!  whoo-hoo!

Comment 7

[rickg]

moving all buster m15 bugs to m16.

Comment 8

[buster]

redistributing bugs across future milestones, sorry for the spam

Comment 9

[Hixie (not reading bugmail)]

As per meeting with ChrisD today, taking QA.

Nominating nsbeta3; this is a serious CSS1 compliance issue which has the 
potential for creating a legacy and which makes a feature difficult to use
in a spec compliant way (namely, floating things around non-floated images).

Comment 10

[Marc Attinasi]

Taking a stab at prioritizing buster's nsbeta3 bugs...

Comment 11

[Jim Roskind]

PDT was tempted to downgrade, but couldn't tell how desirably useful this 
feature is.

Comment 12

[Hixie (not reading bugmail)]

The main problem with this is that if we don't fix this, then when we _do_ fix 
it, any pages relying on our current broken behaviour will end up having images
overlapping each other.

For example, go to the test page:
   http://bugzilla.mozilla.org/showattachment.cgi?attach_id=4065
At the moment, the graphics sit next to each other. This is actually incorrect,
and once we correct it, anyone who is depending on this behaviour will end up
having overlapping images.

Hence, I would say that this destroys this feature of CSS1. (Floating block
level elements that happen to be images.)

So the real problem is not that authors cannot get the correct result, but that 
authors are likely to get the current, buggy rendering, think it's good, and 
design their sites with it this way... then when we fix it, boom go their 
images, sliding under the floats.

Comment 13

[buster]

This is a dup of bug 18445.  Same root cause, even thought they involve
different elements.

*** This bug has been marked as a duplicate of 18445 ***

Comment 14

[Hixie (not reading bugmail)]

Yep.