Skip to main content
M_Boyd
Inspiring
August 21, 2013
質問

After applying the fix for the IE 10 problem, no topic is displayed in the right pane

  • August 21, 2013
  • 返信数 1.
  • 2199 ビュー

The background:

  • We create WebHelp using RoboHelp 10.
  • It's a merged help system that uses a script (from Peter Grainge's site) to redirect from the parent start page to the initial topic.
  • The help is deployed in a web-based application.

I applied Adobe's fix for the IE 10 display issue (the one that should fix the generated help). Then I regenerated the help and added the updated files to the product build. I'm seeing different behaviors. depending on how I access the build.

Accessing the help from the product:

When I run the product in IE 10 and click the Help button:

  • The right pane is initially empty and is gray (instead of the default white background):
  • If you click a topic in the Contents, the right pane doesn't change.
  • You can do either of the following to display the currently selected topic:
    • Resize the browser window.
    • Click a different tab in the navigation pane (Index or Search).

After you take either of those actions, everything seems to work as expected.

Running the help stand-alone:

If I run the generated help by opening the start page in IE 10, the right pane displays the initial topic as expected. However, I still experience the original problem. For example, clicking a link from the search results does not display the topic until the pane is resized.

Has anyone else seen this behavior? As a fall-back, we can add the meta tag to emulate IE 9 to our compiled start page. But, of course, we would prefer a different solution since any post-generation step could be forgotten in the scramble to get a release out.

Thanks,

Melanie

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

返信数 1

Peter Grainge
Community Expert
Community Expert
August 22, 2013

If you applied the Rh10 solution to the install files, you don't need to apply the other fix. Maybe applying both is the issue?


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.
M_Boyd
M_Boyd作成者
Inspiring
August 22, 2013

I applied only one fix for the IE 10 problem -- the fix that's supposed to make subsequently generated files behave correctly. Then I added my regenerated help files to the product build system (so that I could access the regenerated help from the product the next day).

Peter Grainge
Community Expert
Community Expert
August 22, 2013

Peter, I cleared my browser cache, so I'm not looking at a cached version.

I generated the Web Help version of the EmployeeCare sample project, and it opens in IE 10 without any problems.

I think it's the redirect script in the parent project of our merged help system. I just tried opening a child project, and it's fine. But opening the start page for the parent project produces the problems described above.

Do you know whether other people producing merged help have been able to apply this fix?

And if it is the redirect script, are there alternatives for producing merged help that we should investigate? We set up the merged help system many years ago (and several RH versions ago). It has worked perfectly up to now, so we haven't had any reason to change it. (Many thanks for that, by the way! Your site was a lifesaver when we were setting the initial help system up.)


I will double check that merged help is still OK but I do believe I tested it with IE10.

Meantime the fact you say you set this up many years ago makes me wonder if you are using the metatag redirect or the later script. Please revisit my instructions and check that out as I will not be testing tonight. There is a section specifically mentioning this change.


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.