Closed
Bug 187124
Opened 22 years ago
Closed 10 years ago
news.com.com - bad nesting of SPAN and P tags
Categories
(Web Compatibility :: Site Reports, defect)
Web Compatibility
Site Reports
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: mentin, Unassigned)
References
()
Details
(Keywords: top500)
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20021229 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20021229 At this CNET page, all the text in the left column with dark green background is wtite in IE. In Mozilla, the text in first paragraph is white and text in others is black. Reproducible: Always Steps to Reproduce: 1. Open http://news.com.com/2009-1001-978164.html?tag=fd_lede2_hed Actual Results: Text is black Expected Results: Text is white This seems to be caused by improper nesting of <p> and <span> tags. I created a little repro below. In IE both TEXT1 and TEXT2 are on yellow background, in Mozilla only TEXT1. <html> <HEAD> <STYLE type="text/css"> .Q { background-color: yellow; } </STYLE> </TITLE> </HEAD> <body> <p> <span class="Q">TEXT 1</p> <p>TEXT 2</p> </span> </body> </html>
Comment 1•22 years ago
|
||
Parser. No way for layout to do anything different with the content model we create... For what it's worth, I think IE's rendering is pretty broken and that ours is more correct given that markup....
Assignee: font → harishd
Component: Layout: Fonts and Text → Parser
OS: Windows XP → All
QA Contact: ian → moied
Hardware: PC → All
Comment 2•22 years ago
|
||
I think Mozilla doing fine: span is inline-object, wich mean that it it "text" stuff, and </p> are finished current text-line. BTW, this is bad code -- End tag required for span (http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.4)
Comment 3•22 years ago
|
||
I don't think parser can reasonably cope with this in a different way. ->Tech Evang
Assignee: harishd → susiew
Component: Parser → US General
Product: Browser → Tech Evangelism
QA Contact: moied → zach
Version: Trunk → unspecified
Comment 4•22 years ago
|
||
This may be related: From http://davebarry.blogspot.com: <html> <!-- snip --> <style> <!-- .date {FONT-FAMILY:Verdana, Geneva, Arial; FONT-SIZE: 12px; COLOR:#000000; FONT-WEIGHT:bold; } .post {FONT-FAMILY:Verdana, Geneva, Arial; FONT-SIZE: 11px; COLOR:#000000; } .time {FONT-FAMILY:Verdana, Geneva, Arial; FONT-SIZE: 9px; COLOR:#000000; } .archive {FONT-SIZE: 9px; COLOR:#000000; } --> </style> <!-- snip --> <blockquote><a name="88103340"><span class="post"><b>FORNIA NEWS UPDATE</b><br><p>The local TV morning news here had a <i>detailed</i> report today on the fact that this is the 50th anniversary of <a href="http://www.peepresearch.org/">peeps</a>. </span></a><br> <!-- snip --> Everything before the "peeps" link renders normally, but then the "peeps" is rendered in a default font. Similar behavior was noticed in other posts on the page, where everything after the link and before the end of the span was rendered in the default font, rather than the div font. Related?...
Updated•22 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 5•21 years ago
|
||
I also hit the problem on Dave Barry's blog (comment 4) and filed it as bug 205749.
Comment 6•21 years ago
|
||
tech evang june 2003 reorg
Assignee: susiew → english-us
QA Contact: zach → english-us
Summary: Formatting of nested SPAN and P tags - broken? → news.com.com - bad nesting of SPAN and P tags
Comment 7•15 years ago
|
||
still broken
Comment 8•13 years ago
|
||
This bug is still here. However, as per comment 2, I'm not sure this is a real bug. I'm going to attach a pair of testcases, just for reference. P.S.1 FYI WebKit (Google Chrome 15) behaves the same as Firefox while Trident (IE8) and Presto (Opera 11.5x) behave different. P.S.2 Firebug incorrectly places the </span> tag.
Comment 10•13 years ago
|
||
As per comment 7.
Comment 11•10 years ago
|
||
domain doesn't exist anymore
Assignee: english-us → nobody
Status: NEW → RESOLVED
Closed: 10 years ago
Component: English US → Desktop
Resolution: --- → INVALID
Assignee | ||
Updated•5 years ago
|
Product: Tech Evangelism → Web Compatibility
You need to log in
before you can comment on or make changes to this bug.
Description
•