> You and ahmoacah should try building your own browser. I'm sure we'd all use it. Then you can see what the issues are in making one work correctly.

I concur. I don't expect it, but I concur. :-)

> I've *always* wondered what the hell the problem was with browsers, and why browser incompatibilities exist. My limited understanding of the issue is that yes, there are standards for http and javascript, but hardly any browser actually implements them properly.

I think you hit the nail on the head here. I spend a lot of my HTML time reading up on standards and accessibility issues, and a frightening number of non-standard stuff is accepted and/or encouraged by Netscape and IE. I'm not too familiar with many others, but I'm sure the problem is universal. The other thing is that since very few people know how to write proper HTML, browsers are designed to fix people's HTML errors and make the page readable. (I even know of one site where most of the stuff is good, except that the guy treats P tags like double BR tags in his HTML primer. Terribly shoddy. I don't think he even knows that there IS a /P.)

The end result is a world where no two browsers work anything like one another OR the official HTML standard, and where instead of forcing people to code better to be read, browsers allow people's poor code to be read. I think the problem has been snowballing for years. I see non-standard stuff everywhere, now... And Microsoft is a big perpetrator. Go to http://www.htmlhelp.com and run http://monkeyman.niveous.net/resume/index.shtml through the HTML Validator found in Tools to see how much concern for HTML standards Microsoft has.

> -- Dave

Don "That rant got way off topic, but this topic has been driving me nuts lately. Sorry." Monkey