"L. David Baron" schrieb:
> 
> On Wed, 6 Jun 2001, Matthias Gutfeldt wrote:
> > Hmm, from what I read at
> > <http://lxr.mozilla.org/seamonkey/source/htmlparser/src/nsParser.cpp#586>
> > I thought the W3C behaviour is reserved for the "strict" mode:
> >
> > 1. compatibility-mode: behave as much like nav4 as possible (unless it's
> > too broken to bother)
> > 2. standard-mode: do html as well as you can per spec, and throw out
> > navigator quirks
> > 3. strict-mode: adhere to the strict DTD specificiation to the highest
> > degree possible
> 
> The strict mode described here (fortunately) doesn't exist anymore
> (except it's used by the editor).  See
> news://news.mozilla.org:[EMAIL PROTECTED]
> and the thread following.

Hmm, thanks. Where and how is the most current status of the code
documented? 

Another question: From what I figured out by reading the comments in the
nsparser, an unrecognized doctype that uses the right syntax will
invariably trigger standard mode. But "standard" according to what DTD?
My guess is one of the W3C DTDs, but which one? Or does the browser
actually validate the document against the referenced DTD?

There is a large number of really old Doctypes (e.g. in the SGML catalog
for the W3C validator, <http://validator.w3.org/sgml-lib/catalog>), and
quite a few of them will surely trigger "standard" mode just because
they use the right syntax. Therefore it would IMHO make sense if the
parser had a catalog of old Doctypes, and invokes "quirk" modes for
these. Perhaps it does, and I just couldn't figure it out?


Matthias

Reply via email to