Closed
Bug 10049
Opened 25 years ago
Closed 25 years ago
Incorrect Page Layout
Categories
(Core :: DOM: HTML Parser, defect, P3)
Tracking
()
VERIFIED
FIXED
M13
People
(Reporter: quake2guy, Assigned: harishd)
References
()
Details
Attachments
(1 file)
316 bytes,
text/html
|
Details |
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 quake2guy@hotmail.com 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).
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 4•25 years ago
|
||
Updated•25 years ago
|
Status: VERIFIED → REOPENED
Comment 5•25 years ago
|
||
In standard mode, SPAN element SHOULD NOT contain the BLOCKQUOTE element. But SPAN contains BLOCKQUOTE even if we are in standard mode. 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: 25 years ago → 25 years ago
Resolution: --- → FIXED
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 9•25 years ago
|
||
With the Jan 05 build, this problem has been fixed.
Comment hidden (collapsed) |
You need to log in
before you can comment on or make changes to this bug.
Description
•