Orphan Pages in Frameset - HTML forum at WebmasterWorld - WebmasterWorld

Forum Moderators: open

Message Too Old, No Replies

Orphan Pages in Frameset

joanthenod

9:23 pm on Apr 8, 2003 (gmt 0)

10+ Year Member

I am trying to use the javascript mechanism identified in [webmasterworld.com...] to force orphan pages into a frameset on my site, but I am hitting a snag with my navigation bar when the frameset is forced. Normally the following code goes into the 'content' page to ensure that the navigation menus/sub-menus are visible across 2 separate frames (ie. 'menu' and 'content')

<body onload="javascript:{if(parent.frames[0]&&parent.frames['MenuBar'].Go)parent.frames['MenuBar'].Go()}">

However when I use the orphan frames mechanism to force pages into a frameset the submenus are not rolling over the 'content' page but appear to be restricted within the 'menu' frame...and this makes the navigation bar unusable.

The problem can be seen at the following, where the orphan page frame forcing is being tested:
<sorry, no URLs>
The correct running of the navigation bar can be seen on the main site:
<sorry, no URLs>

Any suggestions on how this can be solved would be welcomed.

Many thanks

[edited by: tedster at 9:37 pm (utc) on April 8, 2003]

tedster

9:51 pm on Apr 8, 2003 (gmt 0)

WebmasterWorld Senior Member

10+ Year Member

Congrats on getting a DHTML menu cascade to overlap into a second frame at all!

It seems strange that forcing a page into a frameset would give a different result than displaying it initially within the "hard coded" frameset. It seems almost certain to me that the dynamically created frameset must show some difference in the actual code - else it would work identically.

So I'd start by comparing the source in both cases and seeing what's different.

tedster

12:52 am on Apr 9, 2003 (gmt 0)

WebmasterWorld Senior Member

10+ Year Member

I've been thinking about this some more. Since it's so uncommon to have a div that's created in one frame be able to overlap into another frame, you should begin by focusing on how your particular DHTML makes that possible on your regular frameset.

Then let's look at why that part of the code doesn't import correctly into your dynamically generated frameset.

joanthenod

8:48 pm on Apr 9, 2003 (gmt 0)

10+ Year Member

Thanks, I have looked at the .js file that the script draws on to generate the menus and within it there are some variables declared:

var FirstLineFrame='MenuBar'; // Frame where first level appears
var SecLineFrame='MainPage'; // Frame where sub levels appear

I imagine this is where the problem is as on the dynamically generated framset the 'MainPage' would not be the frame displayed...so how do I go about accommodating this, can I declare an alternate to 'MainPage' and let the script accept either(and if so how would this be done)

The navigation menu system was a freebie download, not one that I scripted...that is well beyond my capabilities (as you can no doubt tell)

Thanks