The real problem is not ND and frames but rather the browser and HTML
implementation of frames. The one thing to be very careful about is that
frame handling while greatly simplified using Dynamic HTML is not
handled consistently across browsers (Netscape & IE).
Consequently, we have had to disable all dynamic HTML to make sure
the frame handling works properly. You must pay a lot of attention to
the targets for it to work properly. Assuming standard HTML not
dynamic HTML, what frame loads after a button click depends on the
target value of the form tag for the page.
We have ended up changing some buttons to HREF's to overcome this
limitation since the page will always go to the same target no matter
how many possible desinations you really want when using buttons.
HREF's each have their own target property so can go to different
frames easily. Also, unless you are using dynamic HTML you cannot
change the target after the page is rendered to the browser in the web
event for either a button or href. Any specified target is ignored and the
browser uses the target specified on the page as it was displayed.
We use a number of nested framesets in our application and they work
very well. We display a navigation bar in a frame across the top of the
app that only reloads if the re-login to the application while the rest of
the window updates. It took some trial and error to get all the targets
working correctly and even some manual overrides of the form tags
since ND didn't want to allow me to always specify the form target but it
does work.
Hope this helps
--Bill Froelich
<< On 9 Apr 99, at 12:10, Mathew, Aby wrote: >>
> Frameset behavior seems to be inconsistent and troublesome, probably one
> more reason to replace them with tables as suggested by a recent posting by
> Joel.
>
> Going by the docs, I can't see a load() method which can understand
> ***load("myNewFS","_top")***
>
> load(String, String) is
>
> public int load(String targetHtmlFrameSetName,
> String targetHtmlFrameName)
>
> which means load page in targetHtmlFrameName, part of
> targetHtmlFrameSetName.
>
> Whenever I try loading a frameset using the above method, it always loads on
> the window top, by default. (I am using Netscape Navigator 4.04)
>
> However, if you can replace the button with an Href and have an extraHtml
> TARGET=_TOP, you are very likely to get to the top of the window.
>
> Good luck.
>
> Aby
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, April 09, 1999 10:34 AM
> To: [EMAIL PROTECTED]
> Subject: [ND] how to load a new frameset in "_top" from a
> button click in a specific frame?
>
> I am about fed up with ND and frames.
>
> I am trying to do the following:
>
> I currently have a frameset with 4 frames loaded into the browser
> window. When I click
> a button in one of the windows, I want a new frameset to be
> loaded in the browser
> window. (I have resorted to loading entire framesets
> because I couldn't get specific
> frames to load correctly.)
>
> When the button is clicked, I return the command
> load("myNewFS","_top"). It insists on loading the frameset in the window
> from which the button was clicked.
>
> I have tried all kinds of things, and have not had any luck.
>
> Can anyone shed any light on this?
>
> Thanks!
>
> - Darby O'Connor
>
> _________________________________________________________________________
>
> For help in using, subscribing, and unsubscribing to the discussion
> forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
>
> For dire need help, email: [EMAIL PROTECTED]
----------------------------------------------------------------------
Bill Froelich [EMAIL PROTECTED]
Client Server Technologies, Inc. 847.397.7300 x24
http://www.cstech.com
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
