On Dec 8, 9:01 pm, Bergamot <berga... (AT) visi (DOT) com> wrote:
Quote:
it trigs CSS1Compat mode
Huh? That's an IE-centric thing. Your complaint was about Firefox,
so this weird mode has no bearing on the issue. |
I complained about nothing at all in this thread.
OP had a problem with Gecko rendering, I gave some ideas about it, you
said that quirk mode may also affect on the behavior, I explained that
the page in question is in so-called "CSS1Compat" mode so quirk mode
is not here. So the only person here who raised the DOCTYPE question
in this thread is you so far ;-)
You have my word on it it does :-) The only change is the fixed bug
with XML declaration in pseudo-XHTML pages that kept IE6 in BackCompat
mode.
Quote:
which is the standard regulation paper now as all other
browsers are using the same tables.
Oh really? |
Absolutely. The browser market is a _market_ - too bad, stubborn,
lazy, stupid, slow or unprofessional are going out - no W3C no W33C
are able to help them.
This is a completely different document you are linking. It is the
same as to take a DOM specs and a test table from quirksmode.org
The first one is what _should_ be, the second one is what it _is_.
The same
http://msdn2.microsoft.com/en-us/library/bb250395.aspx is
_should_,
http://hsivonen.iki.fi/doctype/ is _is_. Overall all serious
browsers are standard compliant in this aspect: except some old and
not supported anymore like IE5 for Mac.