The concept of industry standards seem completely lost on MS, but at this point in time if it doesn't work in IE then you loose a massive percentage of your audience.
Having said that, you can generally fiddle the code to make 95% or more of it work in most browsers... although that generally ends up making the code bulky and hard to manage. You just have to weigh up time vs. customer base. If you're selling something on the web, how many customers will have problems with the site... and of them, which would be unlikely to be able to fire up another browser to try again?... The point is that I could write a basic site in a few hours, but could spend another day trying to get it to work in Opera, NeoPlanet, Netscape, Konqueror, etc... Is it really worth it (other than from a self-satisfaction point of view)? Steve -----Original Message----- From: Carl Cerecke [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 11 December 2001 11:28 AM To: Yuri DeGroot Cc: [EMAIL PROTECTED] Subject: Re: Web browsers, was Re: HW suppliers Yuri DeGroot wrote: > Being a person I'm kinda biased and I reckon the tool should be the > one to change :-) Being a person who writes software, I'm kinda biased and I reckon the tool should implement the standard and the person should stick to the standard. Standards should be well defined and easy for the user and implementor. In other words, if your 'standard' is "What works in IE" then that's bad. Cheers, -- Carl Cerecke, Assistant Lecturer|email: [EMAIL PROTECTED] Department of Computer Science, |Phone: +64 3 364 2987 ext. 7859 University of Canterbury, |Fax: +64 3 364 2569 Private Bag 4800, |http://www.cosc.canterbury.ac.nz/~cdc Christchurch, New Zealand. |
