- From: David Woolley <david@djwhome.demon.co.uk>
- Date: Fri, 28 Dec 2001 18:53:17 +0000 (GMT)
- To: w3c-wai-ig@w3.org
> I mean: it's up to browser not to render broken content. > The fact that MS IE and Netscape render broken content doesn't say anything > good in their favour. Rendering broken content is commercially sound. It avoids people blaming your software for what are really authors' mistakes and it reduces your support costs. The evolutionary pressure is to cope with at least as broken content as your competitors. It is also compatible with one of the core internet principles, which is that you must be correct in what you send (authors should produce correct HTML) and tolerant in what you accept (browsers should work with broken HTML).
Received on Friday, 28 December 2001 17:00:24 UTC