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 7463 - CONTENT_FORMAT_SUPPORT-3: "No doctype found" is triggered when doctype is invalid.
Summary: CONTENT_FORMAT_SUPPORT-3: "No doctype found" is triggered when doctype is inv...
Status: RESOLVED FIXED
Alias: None
Product: mobileOK Basic checker
Classification: Unclassified
Component: Java Library (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: fd
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-31 07:56 UTC by fd
Modified: 2010-08-30 12:07 UTC (History)
0 users

See Also:

Attachments

Description fd 2009-08-31 07:56:38 UTC 
When the doctype declaration contains a syntax error, the XML parser fails to identify it as a doctype declaration and the mobileOK Checker reports:
 1. a markup validation error for the syntax error. That is correct.
 2. a "no doctype found" error. That is a bit misleading, and should probably be removed.

See discussion in:
http://lists.w3.org/Archives/Public/public-bpwg/2009Aug/0025.html

Francois.
Comment 1 fd 2010-08-30 12:07:25 UTC 
A "present" attribute is now added to the doctypeDecl element in the moki representation of the page under test. This attribute contains "true" when something that looks like a DOCTYPE declaration is detected in the page under test, for instance:

<doctypeDecl
  present="true"
  publicID="-//W3C//DTD XHTML 1.0 Strict//EN"
  systemID="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd" />

This attribute is then used to trigger CONTENT_FORMAT_SUPPORT-3 accordingly. The detection of "something that looks like a DOCTYPE declaration" is based on the following regular expression (case is ignored):
 <!doctype\\s