User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030312 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030312 Just Create an HTML like showed afterwords, and you will see that CSS doesn't honors the width and height sizes. IE renders fine: <html> <body> <div style="display: inline; height: 110pt; width: 200px;"> Block N. 1 <br> Begin_I.jpg <br> (360x238) </div> <div style="display: inline; height: 110pt; width: 200px;"> Block N. 2 <br> logo.jpg <br> (348x316) </div> <div style="display: inline; height: 110pt; width: 200px;"> Block N. 3 <br> break.jpg <br> (283x212) </div> </body> </html> Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: Bad rendering Expected Results: boxes should be rendered at the same line one after the other, look at ie
> boxes should be rendered at the same line one after the other, look at ie This is a bug in IE. See http://www.w3.org/TR/CSS21/visudet.html#propdef-width : Applies to: all elements but non-replaced inline elements, table rows, and row groups In this case you're dealing with "non-replaced inline elements". http://www.w3.org/TR/CSS21/visudet.html#propdef-height has similar language.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → INVALID
OK, But replace span with button and put some images inside the button. and Mozilla continues rendering bad. Look at http://www.webreference.com/dhtml/column29/4.html with IE and mozilla Should I reopen the bug?
That page has nothing to do with this bug. What's happening there is that the page specifies no width for the float, which means "shrink-wrap width". The site puts a "NOWRAP" attribute on the div containing the buttons, but no such attribute exists. So we line-wrap the buttons to honor the shrink-wrap width.
Oh Great GURU!!!. My apologies. You're right as always. What I described here is a bug on Mozilla 1.1a Mozilla 1.2 and 1.3 works very fine. Sorry for the spam and my congratulations for you knowledge. Abandoning DEFINITLY this bug...
You need to log in before you can comment on or make changes to this bug.