- From: Ian Hickson <py8ieh@bath.ac.uk>
- Date: Wed, 26 Jul 2000 19:18:07 +0100 (BST)
- To: Matthew Brealey <webmaster@richinstyle.com>
- cc: www-style <www-style@w3.org>, www-html@w3.org
On Wed, 26 Jul 2000, Matthew Brealey wrote:
>
> Is it:
> (a) legitimate for browsers to employ doctype-detection in order to
> trigger more (CSS) bugs?
Given the higher goal of infiltrating the market with a standards
compliant browser, and the requirement for mass market acceptance to
reach that goal, and the expectation in the market that browsers will
keep rendering existing pages as they always have done, I believe that
it is sensible to use the DOCTYPE (or lack thereof) to decide whether or
not to render pages in a strictly compliant way or a backwards
compatible way, yes.
It has to be pointed out that DOCTYPEs in general have relatively good
correlation with the level of standards compliane of pages.
What other solutions are there?
> (b) really an error response to HTML to break CSS?
Like I said, the error response to HTML errors is undefined. Browsers
can do virtually *anything* with invalid HTML documents and still be
compliant.
--
Ian Hickson __..--''``---....___ _..._ __
/// //_.-' .-/"; ` ``<._ ``.''_ `. / // /
///_.-' _..--.'_ \ `( ) ) // //
/ (_..-' // (< _ ;_..__ ; `' / ///
/ // // // `-._,_)' // / ``--...____..-' /// / // fL
Received on Wednesday, 26 July 2000 14:18:17 UTC