>Don't know whether it's an option but maybe IE handles XHTML better? Somehow I doubt it tho...

One thing that IE does that I have still not been able to do with NS (maybe a setting) is create an object reference to a function object in a parent frame.

In IE with frames I can have a function object in the "parent" frame:
theAPI=createJSFunctionObject()
Child frames can then have a routine that searches through the "document window" ancestors and create reference to the object:
myAPI=window.parent.theAPI
And then run methods contained in the reference:
someResult=myAPI.GetResultJSFunction()

But with NS I have not yet figured out how to do it - or even if it can be made to work. It might have something to do with the iframes. I have also noticed that DHTML (at least my tentative newbie musings into it) performs noticably better in IE. It may be settings. The project specifies IE - for all other business I use NS-8 in firefox emulation. My system has not picked up anything dirty since I installed NS-8. The site specific controls are great.