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

Community Beginner ,
Jul 17, 2019

Copy link to clipboard

Copied

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.

TOPICS
Classic, HTML, WebHelp

Views

690

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Community Professional ,
Jul 17, 2019

Copy link to clipboard

Copied

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

Please use the blue Reply button at the top to help me help you. The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Community Professional ,
Jul 17, 2019

Copy link to clipboard

Copied

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

Please use the blue Reply button at the top to help me help you. The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
A-Bel AUTHOR
Community Beginner ,
Jul 17, 2019

Copy link to clipboard

Copied

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

Viele Grüße

Annette Bellut

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Community Professional ,
Jul 17, 2019

Copy link to clipboard

Copied

I have gone through the Firefox settings and so far I cannot find anything that makes a difference. Pending Adobe looking at this, if anyone does find a solution, please post it here.


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

@petergrainge

Please use the blue Reply button at the top to help me help you. The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Community Professional ,
Jul 17, 2019

Copy link to clipboard

Copied

Got the same problem with my WebHelp located on a LAN server - just a flash of the skin colour & then endless loading. I haven't found how to let FF know that it's a trusted location; thought it might have been the new "blocked content" settings, but the Info icon shows nothing about blocking parts of the page (as the FF help says it should if blocking is turned on).

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Community Professional ,
Jul 17, 2019

Copy link to clipboard

Copied

@Jeff I am guessing LAN server is the same as local for this purpose. It is still working OK from a web server.


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

@petergrainge

Please use the blue Reply button at the top to help me help you. The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Community Professional ,
Jul 17, 2019

Copy link to clipboard

Copied

For a long time I've had a problem with Chrome not loading multiscreen HTML5 properly when run locally. If I allow third party cookies it works fine. (no, it doesn't makes sense to me, but it works) I wonder if its the same problem with Firefox and webhelp.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Community Professional ,
Jul 18, 2019

Copy link to clipboard

Copied

Dug a little into it - it's looping on whproxy.js - throwing a message about "SecurityError: Permission denied to access property "whname" on cross-origin object"

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
New Here ,
Jul 18, 2019

Copy link to clipboard

Copied

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.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Community Professional ,
Sep 12, 2019

Copy link to clipboard

Copied

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"

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Community Professional ,
Sep 12, 2019

Copy link to clipboard

Copied

That's fine when you have control over the user's machine.
Please use the blue Reply button at the top to help me help you. The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Community Professional ,
Sep 12, 2019

Copy link to clipboard

Copied

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

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Community Professional ,
Sep 12, 2019

Copy link to clipboard

Copied

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.
 
Please use the blue Reply button at the top to help me help you. The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Community Professional ,
Sep 18, 2019

Copy link to clipboard

Copied

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

 

Please use the blue Reply button at the top to help me help you. The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
A-Bel AUTHOR LATEST
Community Beginner ,
Sep 25, 2019

Copy link to clipboard

Copied

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

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Community Professional ,
Sep 18, 2019

Copy link to clipboard

Copied

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.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more