Last week I was looking through a javascript primer on the
Web. There are lots of them.
I think I read that one window can refer to another by its
name.
So after you open the WebHelp window (call it 'A'), and then
another window ('B'), a script in the new window can check to see
if window A is open and, if so, to close it. If there is no window
A, the script does nothing.
Also, there may be a way to build the closer into the script
that launches the new window.
I was having this problem when I was trying several
approaches to context help. I mentioned it to the developer of the
main app, and after he built my WebHelp into the package, the
problem went away.
By the way, our approach makes it look like we're simply
substituting the new topic for the one in the open WebHelp topic
pane. I wanted to limit the disturbance on the user's screen and
let her / him navigate within Webhelp without having to go back to
the main app and click the help button on another screen. Also,
this is useful when a topic has links to other topics in the same
help package. They all come up in the same place.
Harvey