Henri Sivonen schrieb:
> 
> In article <[EMAIL PROTECTED]>, Matthias Gutfeldt <[EMAIL PROTECTED]>
> wrote:
> 
> > Of course some of the functionality can be "reverse-engineered" with
> > test cases, but I'd much prefer some real documentation. Any chance for
> > that? Or should we treat Mozilla browsers as a "black box"?
> 
> If you pick one of the doctypes[1] that activate the Standards mode, you
> can find documentation about the expected behavior at http://www.w3.org/

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

I can't figure out what "do html as well as you can per spec" is
supposed to mean. And I admit that even though Netscape 4 is my primary
browser, I don't know all the quirks it's got; so without documentation,
I don't know which mode really means what for my HTML code.

I also wonder how "strict" adherance works for an "unknown" DTD, which
might contain unknown entities. From my tests with a few custom DTDs, I
gather that Mozilla will merrily display my document as if I were
referencing an W3C "strict" DTD, even if my DTD only defined the BODY
entity. Is that the intended behaviour?

 
> [1] http://www.hut.fi/u/hsivonen/doctype.html

Yep, I knew that one, thanks.


Matthias

Reply via email to