- From: Kynn Bartlett <kynn-edapta@idyllmtn.com>
- Date: Mon, 14 Jan 2002 14:46:34 -0800
- To: Access Systems <accessys@smart.net>
- Cc: David Poehlman <poehlman1@home.com>, RUST Randal <RRust@COVANSYS.com>, "WAI (E-mail)" <w3c-wai-ig@w3.org>
At 4:35 PM -0500 1/14/02, Access Systems wrote: >On Mon, 14 Jan 2002, Kynn Bartlett wrote: > > No, the solution is to get you to not be stuck with broken technologies. >Define "broken" technologies Netscape 4. ;) Especially when it comes to HTML and CSS standards. Something is broken if it messes up in unpredictable ways. Something is not broken if it fails predictably and according to spec. For example, Lynx is _not_ broken when it comes to CSS. It does exactly what it is supposed to do -- it ignores it entirely. Netscape 4 is broken with regards to CSS, because in many cases you are left with the choice of "well, do I use CSS according to spec, and watch it break in Netscape, or do I just discard the idea of using CSS and discard the benefits, including accessibility, of a CSS approach?" Something is broken if it forces you to make that decision. Netscape 4 is therefore broken, and Netscape 6 and Lynx are not (at least when we are talking about CSS). --Kynn -- Kynn Bartlett <kynn@idyllmtn.com> http://kynn.com Chief Technologist, Idyll Mountain http://idyllmtn.com Web Accessibility Expert-for-hire http://kynn.com/resume January Web Accessibility eCourse http://kynn.com/+d201 Forthcoming: Teach Yourself CSS in 24 Hours
Received on Monday, 14 January 2002 17:55:01 UTC