Inspiring

Question

All local Webhelp projects does not open anymore since update to Firefox Quantum 68.0

16 replies
1680 views
Translate

We are working with Robohelp 11.

Is the problem known? - a similar problem occured some years ago.

What can we do (beside changing the browser 😉 Our customers often use Firefox as their default.

This topic is closed to new replies. Start a new post to keep the conversation going.

Jeff_Coatsworth

Community Expert

Looks like the fix to the whproxy.js, whstub.js, and whutils.js fixes most of the opening issues, but still chokes on opening index entry topics (provided they are solo 1:1 index:topic - if you have a 1:many topics entry, the selection still appears and works). Even Adobe's solution talks about loosening up that about:config setting in that case.

Translate

Peter Grainge

Community Expert

Adobe have now released a fix for RoboHelp 2015 and 2017.

It can be found at

https://helpx.adobe.com/robohelp/kb/webhelp-output-loading-issue-firefox.html

Translate

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

A

A-BelAuthor

Inspiring

Okay, thank you for that information. Seems to be the moment to think about an update to 2019.

Translate

Peter Grainge

Community Expert

I believe this has been fixed for 2019 and that a fix for RH 2017 and 2015 will be shared soon but not for RoboHelp 11.

Translate

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

According to @jeff.laing.sncr (whose post got lost in the transition) the fix in FireFox is:

"There is a Firefox workaround, which involves relaxing security.

Go to about:config

Locate security.fileuri.strict_origin_policy

Set it to false"

Translate

Peter Grainge

Community Expert

That's fine when you have control over the user's machine.

Translate

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

Yes, I've described it as a workaround for now to my users.

Translate

D

deformd93080388

Participant

According to Mozilla they changed the behavior in Firefox 68 toward local files:

803143 - Local files can access other files in the same directory

Hopefully Adobe can make a fix to allow RoboHelp to continue to work locally.

Translate

Peter Grainge

Community Expert

A quick test shows it is not just RoboHelp 11 where webhelp is broken.

So far I have only tested locally. Have you tried from a server?

I have alerted Adobe.

See www.grainge.org for free RoboHelp and Authoring information.

@petergrainge

Translate

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

Peter Grainge

Community Expert

The problem does seem to be webhelp run locally. I put an output on a server and that is working OK.

See www.grainge.org for free RoboHelp and Authoring information.

@petergrainge

Translate

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

A

A-BelAuthor

Inspiring

Yes, that also what I have tested: only local projects are affected!

Viele Grüße

Annette Bellut

Translate

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.