ljknews wrote: > My experience is that browsers succeed on standards-compliant > pages. Standard compliance should be the first test. If it > subsequently fails on a particular browser, it is a browser > defect which may or may not be of interest to the publisher.
Agreed that, talking only about HTML, browsers are okay with standard page. But nowadays, pages are not only HTML, but CSS, JavaScript, etc. Then the validators are not useful: a CSS will most likely have different rendering even if it's w3 compliant. Then, talking about publishers, of course they care about particular bugs of browsers, and that's why web interface are tough to do! You need to have a good/almost-consistent rendering on different browsers... no matter if they have bugs or not. --Romain http://rgaucher.info _______________________________________________ Secure Coding mailing list (SC-L) SC-L@securecoding.org List information, subscriptions, etc - http://krvw.com/mailman/listinfo/sc-l List charter available at - http://www.securecoding.org/list/charter.php SC-L is hosted and moderated by KRvW Associates, LLC (http://www.KRvW.com) as a free, non-commercial service to the software security community. _______________________________________________
