Elements after DIV with floating IMG incorrectly positioned.

RESOLVED INVALID

Status

()

RESOLVED INVALID
17 years ago
17 years ago

People

(Reporter: kdunz, Assigned: attinasi)

Tracking

Trunk
x86
Windows 2000
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

17 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530
BuildID:    2002053012

The following document is incorrectly displayed. The text after the DIV is
wrapped next to the image even though the DIV's width is set to 100%. IE5 and 6
display the page correctly.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<style type='text/css'>
	img {float: left}
	div {width: 100%}
</style>
<html>
<head><title>Untitled</title></head>
<body>

<div><img src='no.gif' alt='Image goes here'height = '300' width = '300'>
<p>This text and the image are in a div with style given by:<br>
img {float: left}<br>
div {width: 100%}
</p>
</div>

<p>This text is outside of the div and should be placed below the image.</p>
</body>

</html>

Reproducible: Always
(Reporter)

Comment 1

17 years ago
Created attachment 94368 [details]
HTML file given in the description.

Comment 2

17 years ago
Nah, everything floats to the right of the image unless you make a clear:left.

Comment 3

17 years ago
Looked okay with BuildID #2002080711.  For the sake of everything, I tested 
this with Internet Explorer and the output is display exactly the same as I saw 
in this same build.  I'm using IE version 5.00 for testing this one.
moz, opera, konq -> text right of image.
IE5/Mac -> text right of image.

The described behavior of IE/Win is contrary to the CSS2 specification as I 
understand it.
4:1 and a browser not known for good standards is the only one breaking it -
INVALID. Reopen, if you have a good quote from CSS2.0 Spec.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.