Skip to main content
Participant
February 14, 2013
質問

Robohelp displays twice in IE 9 when used in an iFrame

  • February 14, 2013
  • 返信数 1.
  • 1098 ビュー

I am building an application for a client who needs to be able to control access to their Robohelp content.  I am doing this by displaying the Robohelp content inside of an iframe in another page (ASP.NET).  The problem is the entire Robohelp frameset appears twice. The first time it is all stylized right and the second time, it looks like some of the styles didn't apply. It is really wierd and very frustrating. It doesn't do this in Firefox or Chrome -- just IE.  Anybody have any idea how to fix this?

Thanks

このトピックへの返信は締め切られました。

返信数 1

Known Participant
May 7, 2013

Hi.

QA just discovered this problem in the WebHelp I created in RH9. The help system is also displayed in an iFrame, and the frameset displays twice in IE9. The developers don't really know what to do. And I really don't have a solution. So... I was wondering whether you came upon a fix? And if so, do you mind sharing it.

Thanks.

Peter Grainge
Community Expert
Community Expert
May 7, 2013

Can we take it that the help opens correctly if run standalone and the issue is only when the developers but it in an iFrame?

If so, then it's an issue with their work. I don't mean that in an unhelpful way, it's simply it's an issue outside of what we can help with in these forums, unless someone with a developer background is looking in.


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.
Willam van Weelden
Inspiring
May 9, 2013

In that case I'm sorry but I don't know what to suggest. I wonder if a forum aimed at developers would be of more use to you.


See www.grainge.org for RoboHelp and Authoring tips

@petergrainge


Hi,

I just tested several outputs in an iFrame and it worked fine in all browsers (even IE).

What is the SRC of the help your developers are calling? Perhaps you use a call that makes WebHelp behave unexpected.

Greet,

Willam