46475 - DTs can be nested in Strict DTD

Status: VERIFIED WONTFIX

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

Description

[Hixie (not reading bugmail)]

In the Strict DTD, the "<DT>" element is not acting as if it had an optional
end tag. That is, the HTML markup:

   <DT> <DT> <DT>

...is treated three <DT>s inside each other, and not as 

   <DT> </DT><DT> </DT><DT> </DT>

...as it should be.

See testcase:
   http://www.bath.ac.uk/%7Epy8ieh/internet/html40/test41-4.html

Nominating for nsbeta3. This is a serious HTML parsing compliance issue.

Comment 1

[Nisheeth Ranjan]

Ian, please comment if this breaks content on the top 100 sites.  At this point, 
we have tons of other stuff to do. So, we are futuring this for now.

Comment 2

[Nisheeth Ranjan]

This bug has been marked "future" because the original netscape engineer working 
on this is over-burdened. If you feel this is an error, that you or another
known resource will be working on this bug,or if it blocks your work in some way 
-- please attach your concern to the bug for reconsideration. 

Comment 3

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Er... this bug alone calls into question whether the strict DTD is more
standards compliant than the navDTD.  I'd rather see the strict DTD turned off
completely than ship it with this bug.

It's also probably under a 5 line fix.  I think this should be nsbeta3+.

Comment 4

[Hixie (not reading bugmail)]

Of the top100 + all pages to which they link, this affects around 30 of them,
including  house.gov, amazon.com, and the excite classifieds, according to a
very quick text search.

And what David said, too.

Comment 5

[harishd]

The strict DTD is not going to be supported in Mozilla anymore.  Marking 
nsbeta3-.

Comment 6

[rickg]

Marking wontfix. We've decided to punt on strictDTD for 6.0.

Comment 7

[Jan Carpenter]

verified