Closed Bug 10049 Opened 21 years ago Closed 20 years ago
Incorrect Page Layout
In milestone 7, www.q3arena.com was displayed correctly. It does not have the correct layout now. I suspect that this has to do with frames and/or image maps. Also, the text is displayed as the wrong color after a few paragraphs meaning that the site has become unreadable(black on black). Just tryin' to help. Andrew Stern firstname.lastname@example.org http://andrewstern.freeservers.com
Here's a reduced test case: <html> <head> <base href="http://www.q3arena.com/"> </head> <body bgcolor="black"> <span style="font-family: Verdana; font-size: 8pt; color: white; text-decoration: none"> SOCKS proxy: <blockquote>text in blockquote</blockquote> </span> </body> </html>
What's happening is that the BLOCKQUOTE is getting moved outside of the SPAN tag and so there's no associated style info that says that the text should be white and of a particular font Here's a dump of the content model: html refcount=3< head refcount=2< base href=http://www.q3arena.com/ refcount=3<> > body bgcolor=black refcount=3< Text refcount=3<\n\n\n\n\n\n> span style=font-family: Verdana; font-size: 8pt; color: white; text-decorati on: none; refcount=3< Text refcount=3<\nSOCKS proxy:\n> > blockquote refcount=3< Text refcount=3<text in blockquote> > Text refcount=3<\n\n\n\n\n\n> > >
Ok -- I've fixed this by making spans act like blocks. The W3C says spans are inline -- but hey, you can't argue with navigator. (I'll update the DTD to do the right thing in non-quirks mode).
In standard mode, SPAN element SHOULD NOT contain the BLOCKQUOTE element. But SPAN contains BLOCKQUOTE even if we are in standard mode. reopen.
Clearing FIXED resolution due to Reopen.
Harish -- this bug needs to be handled by updating the elementtable using quirks mode. I'll leave it to you.
Status: NEW → RESOLVED
Closed: 21 years ago → 20 years ago
Resolution: --- → FIXED
Fixed by landing of residual style handling.
With the Jan 05 build, this problem has been fixed.
You need to log in before you can comment on or make changes to this bug.