flignar

I have a project that requires frames...it works great in IE but not Firefox (any Gecko) because when I call a parent function from the frame Gecko thinks the base url is in the frame file not the main file...so when I reference graphics/files from the function they are one directory off.

(There are hundreds of frames so they need to be in a folder.)

mackenga

Hmm. I'd try a few more browsers and check to see which behaviour is more common, and maybe take a look at the standard as well to see which one is right. Then your options are to support the standard and let the non-standard browsers flap or do hacks based on determining which user agent is in use so that they both work.

I don't actually know which is the correct, or standard behaviour off the top of my head. If it turns out IE's behaviour is correct (which would surprise me, but it's perfectly possible) then you have less of a dilemma on your hands since the others are likely to inch closer to the same behaviour in future releases. If IE is wrong it is likely it will stay that way in which case your best bet is probably to support it with hacks since MS will never fix it (just say they have a few times).

Oh, and it's up to you, but I'd tend to rethink any design that called for hundreds of frames! Bear in mind that browsing your local copy on a fast machine is going to behave OK, but what happens when they translate to hundreds of HTTP requests, possibly over a slow internet connection, and the page is loading into a slower, older machine?

__________________
"I'm not a genius. Why do I have to suffer?"