ANYTHING works better here than Explorer
My intent is to hang ten on the leading edge of the bleeding edge of what can be done with xhtml and if some browser can't keep up, as long as I am standards compliant, so be it. I develop on Firefox so it will always work. If it is W3C standards compliant any other browser should work. When I have the time, I will go the extra mile to make things cross-browser compliant. But time is limited. The first priority is: get it to run in Firefox. The second is 100% standards compliant. Last is dealing with browser specific quirks. You have been warned.
Firefox is available here
Opera is available here
Safari is available here
Google Chrome is available here
LongwindedeGeekBabble
This site is the garden of Javascript. Since all the other browsers use standard javascript and Explorer uses its own unique dialect, adding Explorer means writing everything twice. And there are things which Explorer just doesn't handle, like the xhtml object element which don't have any good workarounds.
Someday MS may decide to make Explorer standards compliant and the problem will solve itself before I get the Round Tuit attached to this project.
Dec 7 2009. Okay I wrote everything twice. Except for parts of the swamp. Bill owes me.