Closed Bug 25522 Opened 25 years ago Closed 25 years ago

DOCTYPE 4.01 causes a problem with the parser

Categories

(Core :: DOM: HTML Parser, defect, P3)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: chrispetersen, Assigned: rickg)

References

()

Details

(Whiteboard: [PDT-])

Attachments

(3 files)

Build: Apprunner Version: 2000012708 Platform: All Expected results: The parser should ignore a doctype 4.01 element. The TD alignment should apply to a nested table. What I got: The TD alignment is working with a nested table. The table is left aligned instead of center aligned. Steps to reproduce: 1) Open the first test case in Apprunner. This test case includes table inside a table. The nested table should be centered inside the first table. This test case is using a DOCTYPE 4.0 Transitional element. 2) Open the second test case in Apprunner. This test case is identical except that it is using DOCTYPE 4.01 Transitional element. The nested table is not centered.
Attached file Doctype 4.0 transitional (deleted) —
Attached file Doctype 4.01 Transitional (deleted) —
I found this problem on apple's home page so I not sure what other sites may currently use DOCTYPE 4.01.
On to my list.
Assignee: rickg → harishd
Keywords: beta1
Why would you say that DOCTYPE 4.01 should be ignored? Currently, DOCTYPE 4.0x is mapped to strict mode, which I think is correct.
The "Align" property, on TD, is not being applied to the inner TABLE, in STRICT mode. Since the content-model looks correct I'm giving the bug to karnaze.
Assignee: harishd → karnaze
Whiteboard: [PDT-]
We run in quirks vs. non-quirks. Corner case. Putting on on PDT- radar for beta1. Would not hold beta for this bug.
*** Bug 26214 has been marked as a duplicate of this bug. ***
Putting DOCTYPE HTML 4.01 also causes major CSS troubles: <A HREF="http://pages.infinit.net/dacmot/moztest/test.html">4.01</A> and <A HREF="http://pages.infinit.net/dacmot/moztest/test2.html">4.0</A>. It seems like the margin, padding and border-width attributes get totally ignored.
IMO, any doctypes public before final release should be on the compat-mode list. However, that should really be discussed in bug 1312.
The 2nd attachment centers the table when doctype 4.0 is substituted. The table code has no way of distinguishing between doctype 4.0 and 4.01 as far as I know. It does distinguish between navQuirks mode and standard mode, but doctype 4.01 doesn't appear to set the mode to standard. Rick, do you know what is going on here.
Assignee: karnaze → rickg
Fixed in my tree; awaiting opportunity to check in.
Status: NEW → ASSIGNED
Target Milestone: M14
Chris, 4.01 does set the mode standard. I will create an attachment that would trigger standrad mode ( <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> ).
Attached file Strict mode (deleted) —
Fixed by change to parser.cpp
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
verified fixt
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: