Closed Bug 50070 Opened 24 years ago Closed 24 years ago

[STRICT DTD] remove Strict DTD parsing

Categories

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

Product:
Core
Component:
DOM: HTML Parser
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: ekrock, Assigned: rickg)

References

Details

(Whiteboard: [nsbeta3+][PDTP2] fix waiting) 

Strict DTD parsing must be removed for nsbeta3. Assigning to harishd. Harish, if
this is a DUP, just close it. Thanks!
Marking [nsbeta3+].
Keywords: donttest, nsbeta3
Whiteboard: [nsbeta3+]
Status: NEW → ASSIGNED
Whiteboard: [nsbeta3+] → [nsbeta3+] fix waiting
RickG has a fix in his tree, awaiting a good time to check in.
Blocks: 42525
Severity: normal → blocker
*** Bug 42525 has been marked as a duplicate of this bug. ***
No longer blocks: 42525
Could I ask that this be made a pref, at least in Mozilla even if not in NS6?
(I'm fine with defaulting it to off, even for Moz). As a web developer, I want
very much to be *aware* when I break the standards so I can fix them. A pref
that would cause pages to "really break" when I violated the standards, rather
than going into fallback mode, would be a godsend.

The ideal, of course, would be a fix for bug 42286, but please don't remove the
one way developers still *do* have to see when they break the standards.
*** Bug 48114 has been marked as a duplicate of this bug. ***
*** Bug 48651 has been marked as a duplicate of this bug. ***
*** Bug 48114 has been marked as a duplicate of this bug. ***
*** Bug 50985 has been marked as a duplicate of this bug. ***
*** Bug 50985 has been marked as a duplicate of this bug. ***
*** Bug 50985 has been marked as a duplicate of this bug. ***
*** Bug 16934 has been marked as a duplicate of this bug. ***
*** Bug 50692 has been marked as a duplicate of this bug. ***
Harish, Rick: Can you check this in please? This is masking a lot of other
bugs and is causing a lot of duplicates and is generally a pain for QA.

Thanks...
Keywords: mostfreq
Priority: P3 → P2
It's ready, awaiting a preceeding checkin from Vidur.
Vidur? And news on your checkin that is blocking this bug?

(Is there a bug number we can put in the 'depends on' field for this bug?)
PDT agrees P2 after talking to rickg
Whiteboard: [nsbeta3+] fix waiting → [nsbeta3+][PDTP2] fix waiting
This should not be waiting on anything from me. Based on the response to David
and Ian's question to the HTML WG, the only change that needs to happen is in
the parser. We don't have to do any sniffing for documents delivered as
text/html - all such documents should go through exactly the same codepath -
NavDTD and HTMLContentSink.

Rick and I spoke about this several days ago. At the end of the conversation, I
assumed he understood that there was no need for code change outside the parser.
Rick understood perfectly. At the time of the comment, we were still awaiting 
Vidur's changes. Then the decision to use the html codepath was made. We're no 
longer waiting on vidur, and I'm prepared to land the change momentarily.
Done.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.