Volker> I would be interested in a lesson explaining precisely Volker> what doesn't work with every browser, and how that affects Volker> the usability of a web site beyond the trivial.
Proprietary tags. You are right when you say shite tools spit out shite code. Especially tools made by the same vendor who wants their browser to be the only one used. Kerry> If a web designer is commissioned to design an e-commerce Kerry> site then they must ensure it will work on all browsers. Kerry> Anything less is cheating the client. If you're talking about someone who's *paid* to design web pages, then you are right, of course. Unless the person who's paying doesn't care about non-MS-users. If the person footing the bill is the tax-payer, then we must *demand* open standards, but that's for a different mailing list. Carl> Likewise. The problem arises when IE's way of interpreting Carl> mistakes becomes a `standard`. And people don't see (or learn Carl> from) their mistakes because `it works in IE, so it's OK'. Carl> Carl> > Sorry, Carl, I know this means more work for you as a programmer. Carl> Carl> My PhD thesis (nearing completion) is in this sort of area: Carl> "Error repair in LR parsers". Although I'm dealing more with Carl> syntax errors in programming languages than HTML, the principles Carl> are the same. I'd like to see your thesis when it's done. Sounds interesting. Yuri This email together with any attachments may contain privileged and confidential information. If you are not the intended recipient please notify the sender and delete the message. Any views or opinions presented are solely those of the author and will not necessarily reflect the views of NGC.
