On Thu, Feb 20, 2003 at 11:17:46AM -0500, Matthew Weier O'Phinney wrote: > And, contrary to popular belief (hint: sarcasm!) coding > standards-compliant HTML and CSS does not mean that if "it works in one > browser, than[sic] it'll work anywhere." Not all browsers implement > standards the same or correctly -- OK, then people with broken browsers or webmasters noticing such bugs in W3C compliant pages should be filing bug reports with the vendors. The more reports, the more likely the vendor is going to get off thier ass and fix thier broken software. At this point, if you can't render XHTML 1.1, its broken. Life is too short to bend over backwards for the lazy. > and, with the number of older > browsers out there, you have to be worried also about graceful > degradation of the code so that bugs in older browsers don't make a site > unreadable. At this point, HTML 4 has been deprecated in favor of XHTML 1.x, and has been for three years. If you can't be bothered to update your browser once in three years, why should everybody else bend over backwards to use obsolete standards? -- .''`. Baloo <baloo@ursine.dyndns.org> : :' : proud Debian admin and user `. `'` `- Debian - when you have better things to do than to fix a system
Attachment:
pgpK_SKp0lUJg.pgp
Description: PGP signature