This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 14409 - dt element's content model is incorrectly reported
Summary: dt element's content model is incorrectly reported
Status: RESOLVED FIXED
Alias: None
Product: HTML Checker
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 major
Target Milestone: ---
Assignee: Michael[tm] Smith
QA Contact: qa-dev tracking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-08 07:57 UTC by jrhodes
Modified: 2015-08-23 07:07 UTC (History)
0 users

See Also:


Attachments

Description jrhodes 2011-10-08 07:57:27 UTC
** Overview:

The HTML5 validator incorrectly thinks that the <dt> element's content model is 'phrasing content' even though the specification lists it as a 'flow content'

** Steps to reproduce:

1) Validate http://www.indieup.net/ against the HTML5 validator (http://validator.w3.org/check?uri=http%3A%2F%2Fwww.indieup.net%2F).

** Actual results:

The HTML5 validator states:

"XHTML element p not allowed as child of XHTML element dt in this context.

Contexts in which element p may be used:
Where flow content is expected.
Content model for element dt:
Phrasing content."

** Expected results:

The HTML5 validator should not complain about <p> elements nested inside <dt> as the content model per specification permits it.

** Additional information:

When checking the content model for the dt element at http://www.whatwg.org/specs/web-apps/current-work/#the-dt-element, it clearly states that the content model is flow content, and does not forbid flow content descendants.  Hence, the inclusion of a <p> element inside <dt> should be valid according to the specification.
Comment 1 Michael[tm] Smith 2011-10-24 12:05:05 UTC
That change was made to the HTML spec just a few days ago.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13201
http://html5.org/r/6618

I've filed a bug for this in the validator.nu bug tracker and will try to have a fix for this checked in to the validator.nu sources within the next few days. Feel free to add yourself to the Cc field there:

  http://bugzilla.validator.nu/show_bug.cgi?id=868

After I get the fix made, I'll push it out to the HTML5 backend for the W3C validator.