>Well, somebody is not compliant. Go to my test site and check out this application I'm working on. Open in Netscape then open in IE. You will see the all the sytle and positioning attriburtes don't hold for aspserver controls. Only the html controls hold. Also, on the login try loging with blank username and password. You'll see the form gets submitted even though validation failed.
>
>cbfctest1.dynip.com/wwatsclient/login.aspx
>
>use 'cbf' as username and muffin as 'password'
>
>Charlie

Yea, thats pretty bad but from experience it's what I expected to see.

As I mentioned in my other reply the validation is being performed on the server side for browsers other than IE, again that is by design. I would have hoped that client side support for the newer generation of browsers would have been provided.

As for the layout rendering differences between browsers, your best bet is to drop the grid layout and switch to flowLayout mode. If you intend to target browsers other than IE then this is the only way to go. For gridLayout to work in older browsers such as Netscape 4.x you have to change the targetSchema and the results are typically just as bad.

As you are seeing there are other problems such as setting control widths that still have to be addressed. You can fix these by applying the required attributes from code. For example to size a textbox control that will hold in Netscape add the size attribute.

ie. In the page load: MyTextBox.Attributes.Add("size", "10")

I do agree that there is much room for improvment on cross browser support. If Microsoft is not willing then I suspect we will see developers writing their own custom controls that will.