You didn't mention, but it sounds like you are using WebHelp as your output?
CSH can be created two ways (at least!) There is the WebHelp API which is provided with RoboHelp X5 and there is the method described by Peter Grainge on his website (linked below)
Meanwhile, here is Peter Grainge's article on various methods of calling WebHelp:
Hope this helps.
Wow! Quick reply, and helpful. Thank you, John.
Oops, yes, sorry I forgot to mention that the output for our online help is WebHelp as provided with RoboHelp. Conditional build tags have never been implemented; we generate only one single-source layout per project. "Field level" F1 help consists only of opening the main help topic for a given entry screen. It sounds to me that the bottom line is that it is up to users to close an open help window in order for F1 (Context Sensitive Help) to open the proper help topic from a new entry screen. This could be either from the "Close this Window" button you suggest or by simply using the Close ("X") button. Because of browser variability, however, there is no way to "fix" the help so that it automatically goes from one topic to the next desired topic when F1 is pressed in a new entry screen. Do I understand this correctly?
Thanks again for the help!
Hi, glad I could help.
Not all browsers (or older versions) observe those newer calls dependably. So we are stuck with asking the user to close them. If I understand what you want, you could enable the Show button. This would show the Navigation pane and the rest of the topics so your user could proceed deeper. Still, they will have to close the window! Alternatively you could manually put link "arrows" in the top right of the topic and let them navigate to whatever topic you choose. But, that's time consuming and even this trick is not accessed by F1, so I'm reaching here .
What we really need is a browse sequence button that can be placed in the topic itself rather than those dinky arrows in the Navigation pane. I have requested this feature and maybe you could add your request here https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform&product=38
I think if you take another look at the article on my site that John pointed you to, it mentions the problem of CSH help not working if the help is already open. In our case, the developers played around with their code that calls the help and fixed it. How wouldn't help you but it does indicate that it is something the developers could fix.
See www.grainge.org for RoboHelp and Authoring tips
Thank you, Peter. I'll check into this issue with our development team.