I remember when I first started coding html and I'd get blank pages in netscape, but 
exactly what I wanted in IE, simple things like a forgotten end frame tag....

Having a browser that is standards compliant I agree with, I know M$ make up their own 
versions of standards sometimes, but having a browser with a bit of intelligence to 
second guess things when it gets something that doesn't parse properly would be useful 
in many situations IMHO.

JeremyB.

> 
> From: Carl Cerecke <[EMAIL PROTECTED]>
> Date: 2001/12/11 Tue AM 10:27:46 GMT+12:00
> To: Yuri DeGroot <[EMAIL PROTECTED]>
> 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.      |
> 


Reply via email to