Chris Hoess <[EMAIL PROTECTED]> wrote:
<http://validator.w3.org/check?uri=http://www.mozilla.org/&doctype=HTML+
4.01+Transitional>
> Notice the new selection list for doctypes at the validator; you need to
> use this when checking a page that doesn't have an HTML doctype inline.
That's it! The page was completely valid 'HTML 4.01 transitional' if it
had the proper Doctype declatation included.
So the solution was very simple: Include the declaration and everything
is OK!
It _was_ very simple if the Mozilla developers had not choosen to
(ab)use the presence of a doctype to switch betwheen different rendering
modes (see <http://gutfeldt.ch/matthias/articles/doctypeswitch.html> on
this topic)
Evangelizing Mozilla to web authors is getting hard enough if it comes
to that topic. Those who are used to author for tag-soup-interpreters
rather than for standard compliant browsers even give the advice:
"Leave out the Doctype thing and the page will no more be broken in
Mozilla! Mozilla does weired things if it recognizes a Doctype."
Of cause this is nonsense. Leaving the doctype declaration out switches
Mozilla back to quirks mode which intentionally breaks part of its
ability to render pages in a standard compliant way.
If even [EMAIL PROTECTED] doesn't seem to be able to author pages
for Mozilla in strict mode it throws a bad light on all efforts to
evangelize standard compliant web authoring.
I have just taken a look at http://www.mozilla.org/persistent-style.css
(which is BTW not so easy, see bug #90838). It already seems to contain
all the extra stuff that is needed to be safe from unwanted surprises
people usually get with mozilla in standards mode like
img {vertical-align: bottom;}
Gerv, you suggested in this thread, that you have done very hard cross
browser testing to the site.
What was the reason to exclude the doctype declaration? If it was realy
to prevent the Mozilla Browser from staying in 'standards mode' it was a
shame!
Sorry if you don't like it, but the website of a browser that claims to
start a new aera of standard compliance is more than just documentation.
It has to be the proof and example that authoring for the new aera is
possible and worthy.
Greeting, Michi
--
Beitr�ge zu HTML, CSS und Netzkultur <http://www.subotnik.net/>
Zur �bersicht (keine private Seite) <http://michael.nahrath.de/>
