Closed
Bug 284347
Opened 20 years ago
Closed 19 years ago
MAC-ONLY: DIV tags empty or containing NBSP do not render styles properly
Categories
(Core Graveyard :: GFX: Mac, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: marshak2, Assigned: jaas)
References
()
Details
Attachments
(1 file)
|
718 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Macho-O; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1 This problem is unique to the MACINTOSH version. When rendering a web page, if a DIV tag is empty or contains a non-breaking space, it does not render styles properly. On a Macintosh running Firefox 1.0RC1, compare http://www.wwu.edu:8080/index_broken.shtml to http://www.wwu.edu . Notice how the yellow areas to the left side and the bottom are not yellow on the Macintosh version. The "broken" version contains only non-breaking spaces, whereas the "fixed" version contains "_". Reproducible: Always Steps to Reproduce: Visit http://www.wwu.edu:8080/index_broken.shtml for a working example of this problem. 1. Create DIV tag 2. Attach styles, including background-color to DIV tag 3. Do not populate DIV tag with content Actual Results: Background color did not render properly. Expected Results: It should have rendered the background color. It does for other versions of Firefox.
Comment 1•20 years ago
|
||
Please attach a reduced testcase.
Comment 3•20 years ago
|
||
I believe this is a test case for the reported bug. Modifying this I found with Firefox 1.0.3 for OS X that the last empty div, whether it was written shorthand or with a closing tag, was always rendered, but prior empty divs were only rendered if they were written with a closing tag. I couldn't find anything in the specs that would explain the difference, but I only searched briefly. I found identical results with Safari 1.3, and in VirtualPC with IE6 and Firefox 1.0.3 for Windows.
Comment 4•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Updated•19 years ago
|
Assignee: sfraser_bugs → joshmoz
QA Contact: mac
Comment 5•19 years ago
|
||
So what does that testcase render like on Mac? What is should render as is a 100px tall teal band followed by a 100px tall maroon band. There should be no yellow.
Comment 6•19 years ago
|
||
Indeed, it shows no yellow.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Updated•16 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•