"L. David Baron" wrote (about the amount of code for "quirks" mode):
> 40% sounds very high to me. It could vary a lot depending on how you
> define a quirk. Do you count only features for which there are two
> separate code paths (in which case I'd guess it's only a percent or
> two), or features that exist for backwards compatibility but are not
> standardized (in which case I'd guess it could be more like 10% or 20%)?
> (I don't think calling the global object |window| is required by any
> standard.) If you count DOM HTML (as opposed to DOM Core) as a quirk
> (despite its standardization), then it would be much higher. And while
> we're there, what counts as "layout code"? :-)
As a simple webdesigner, I'd be happy enough with some documentation
that defines what really happens in these mysterious "standard" and
"compatibility" modes. I've read all the articles I could find ("all"
meaning "not very many at all"), but they only provide are listings
about which doctype activates which mode; they never explain what it
actually means. And this is the first time I hear that the DOM is part
of these modes, too.
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"?
Matthias
