David Mann wrote:
BTW the tutor who taught the DW course I went on last year was of the opinion that you should only bother writing for MSIE. And he's done pages for several high-profile businesses.
Sounds like an MS Certified puppet. He might know how to run DW and Frontpage and all the other 'pro' apps, but could he peruse HTML syntax in a text editor and know if its gonna work?
BTW2 the problem with standards is not only getting the web designers/developers to follow them, but also getting the web browsers to format the same HTML in a consistent manner. Oh and actually having complete standards helps (I never want to use frames again).
The problem with standards is that M$ don't like not controlling them. Just look at Javascript..."lets write a slightly compatible thing, call it JScript, and encourage web authors to use that instead of the real McCoy", is how M$ went about that one.
As a result people who want to write dynamic websites often will only do so for MSIE, which again renders websites slightly differently from the W3C HTML 4.x Consortium standard. I have seen Javascript code in M$ sponsored websites that executes a Javascript window.close() upon detecting a non-MSIE browser...
I created a CV for myself using strict HTML 4.x/DHTML/CSS/Javascript on a Windows PC once. I had to make some 'alterations' to the small Javascripts to get them to work properly with MSIE, but once I got them working I then had to transfer the CV to my new linux PC. I found the Javascripts didn't work as expected in Moz/NN, and I had to change them back to the standard. Guys who use Frontpage or DW will not know that their software is creating non-strict code, because the code is automatically generated and therefore mostly hidden from the end-user (not that any guys who are certified in Frontpage/DW etc will actually know how the syntax -should- look...)
It really sucks...
Kind regards,
Chris Wilkinson, Christchurch.
