Then something must be wrong with the JS operation. See, it's heavily based on JS all over, and the display of the menu is dependant on a few JS things too...
But if JS didn't work on your browser, the site should have displayed a warning message ?! :blink: I have personally ensured that each page of HTML code had everything working right, in frames, without them and with the most rudimentary text-based browsers... Back to the drawing board... :ranting: AAARGH!
Wait. Just struck me. Might be that it somehow takes that "parent != self", and if that's so...
Frames Interface, on! 