Skip to main content
Participant
April 10, 2014
Question

WebHelp - With help window open, second application click does not bring help window back into focus

  • April 10, 2014
  • 3 replies
  • 554 views

Hello all,

Using RH11 to create context sensitive WebHelp for use with apigee-to-go console.

Console allows URL calls to launch help in a new browser window (named within the help project).  Works fine except that the browser help window does not regain focus when subsequent context calls are made from the application.

Steps:

  1. With application running in a browser window, I click a help link.  New browser window opens with correct help topic displayed.
  2. Return to application without closing help window.  Application window takes focus; help window moves to back.
  3. I click another help link. Help window does not regain focus.  However, it DOES move to the correct topic.

I've tried lots of things.  Nothing seems to fix this.

For reference, my context call looks like this:

http://<URL>/index.htm#<id=37>>wnd=HelpPopup



Thanks for any help anyone can provide.

Jeff Seltzer

This topic has been closed for replies.

3 replies

Willam van Weelden
Inspiring
April 15, 2014

In your call, you must bring focus to the page with the help. See for

example: http://stackoverflow.com/questions/9008835/bring-popup-to-front

Kind regards,

Willam

seltzerjAuthor
Participant
April 17, 2014

Thanks for the responses, but this doesn't really help.

I'm using a simple URL to make the call.

(That's all I can do within the web app API console I'm working with.)

If I knew how to crack open all of the javascript that RH creates (and had that much time to work on it), I'd try to address it.

I have to give up for now.

I've just appended >>newwnd=false to the end of my calls, so the help appears in another browser tab, rather than its own window.

This isn't great, since each call opens a new tab, but that's better than the help window disappearing behind the sea of open windows most of us have going on, only to cause the user to hunt for it (if they even know it's there).

So, <URL>/index.htm#<id=37>>wnd=HelpPopup

becomes <URL>/index.htm#<id=37>>wnd=HelpPopup>>newwnd=false

Thanks all for your pointers.

If I ever find the time to really work on this issue, I'll post a fix (if there is one).

(Again, I suspect this is just buggy RH javascript.  RH knows enough to update the contents of the help/browser window, but not enough to focus it.)

Best,

Jeff Seltzer

RoboHelp user since v1.1

Peter Grainge
Community Expert
Community Expert
April 12, 2014

Maybe the Calling WebHelp topic on my site will help.


See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
seltzerjAuthor
Participant
April 14, 2014

Thanks Peter.

I've seen your site and it's tremendously helpful.

Unfortunately, it doesn't address my issue.

Robohelp is clearly using some javascript to parse the context ID and call the correct topic in the specified window.

Why it can't focus on the window being called seems strange to me.

Thanks again,

JLS

Peter Grainge
Community Expert
Community Expert
April 14, 2014

Did you see the bit about changing the "#" to "?"  ?

That is really for when using a URL rather than an ID and I'm not a developer so I don't know if it will work there.

If that's not of help, I suggest you take a look at Willam van Weelden's site as he has some more detailed information. http://www.wvanweelden.eu


See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Jeff_Coatsworth
Community Expert
Community Expert
April 10, 2014

Was this ever working for you? I think it’s just a side-effect of WebHelp…