Scripting behavior around frames is not well-defined, and this lack of definition can produce conflicts for scripts that execute while a frameset is loading.
Many browsers also have problems with frameset page scripts that immediately modify frame contents.
These browsers often execute the JavaScript command and then proceed to load the initial src page anyway. And some browsers don't recognize a given frame's existence until its initial src document has loaded. Until that document loads, any script reference to the frame will produce a JavaScript error. The solution to all of these problems is to make sure the frame contents are done loading before you mess with them. Inc. All rights reserved.