www.pantsfactory.org/?action=comments&linkid=1024
Thu, Jan 22, 2004 05:50 PM GMT verbal Back in the days when Netscape was the dominant browser, it was extremely forgiving and accepted alot of malformed HTML, so authors never really learned what was right and what was wrong. Since Netscape was dominant and IE was trying to compete and take that position, IE also had to handle all of the malformed HTML that Netscape handled in the same way that Netscape handled it, thus perpetuating the problem. The problem will now never really go away because in order for any browser to be considered capable, it has to handle everything that the other browsers handle, and it has to handle it all in the same way. Nobody is going to use a browser that wont properly render all of the malformed content that is out there on the web now. It would seem that most authors check their HTML against WinIE rather than a validator that will report errors, and so theyre not aware of their errors. Now that IE is the dominant browser and Microsoft has introduced bugs and malformed content handling of their own, the other browsers Mozilla, Safari, etc.
Whats worse, IE is not even remotely close to being standards compliant in particular, it barely supports CSS1, nevermind CSS2 or CSS3, nor does Microsoft have any plans to implement those standards-there was an article somewhere about this some time ago.
Fri, Jan 23, 2004 02:59 PM GMT burn0ut From recent attempts at working in the sad sad sad field of web technologies, it seems that alot of web designers use microsoft tools frontpage, etc or microsoft centric tools to create webpages. Alot of webdesigners have no idea how to write html, and so theyre at the mercy of these tools.
I whipped the code up for this site in a pretty short amount of time, but that was because I had already spent inordinate amounts of time building the backend that the site is based on. What caused the most grief with building all of the backend support for CGI, templates, JavaScript, etc.
Regardless, browsers still dont generate any kind of error messages for malformed content whether they correct for it or not. Its up to the author to run the HTML theyve authored through a validator if they want to make sure its correct.
|
http://csua.com/feed/