Copy link to clipboard
Copied
Does your WebHelp work well in Microsoft Edge?
On our RH10 WebHelp, TOC pane disappears after using Search function.
After this issue happens, we need to resize the window of Edge or reload the page to display TOC again.
This happens in MS Edge only.
IE11, Firefox and Chrome are OK.
I sent bug reports to Adobe, but there's no answer at the moment.
Do you have any idea?
Thanks.
Copy link to clipboard
Copied
Memory leak? What memory leak? Never heard anything about that…
Copy link to clipboard
Copied
Yes, it causes very little memory leak. Our developers did not allow it even though very little.
Copy link to clipboard
Copied
Is that just with Edge in general or your WebHelp with Edge?
Copy link to clipboard
Copied
I guess the memory leak will occur with the general WebHelp, and browser will not be limited to just Edge.
Copy link to clipboard
Copied
Never heard of any memory leak with WebHelp – I don’t know about your users, but mine will only open the help for a little bit & then close it; only reopening it again if needed.
Copy link to clipboard
Copied
Yes, I also guess almost all the users operates WebHelp like you said. That will not be a problem in MOST cases.
Copy link to clipboard
Copied
How is it afterwards?
Does the whver.js file work well as we expected?
By the way, we have newly devised the proposed changes of whstub.js file.
We tried deleting lines 156-158 instead of line 159.
It seems to work well as of now.
We believe that the memory leak will not occur in this method.
Any JavaScript specialists?
No one?
Copy link to clipboard
Copied
Sorry, I haven't had a chance to try out your solution(s) - I've only just managed to get a Win10 public release machine upgraded to test various versions of RH WebHelp with.
Copy link to clipboard
Copied
Adobe support advised that it would be preferable for me to use Responsive HTML5 instead of WebHelp...
Is it good?
Copy link to clipboard
Copied
It’s certainly the latest new & trendy thing these days (LOL). It’s becoming a widely accepted standard across multiple browsers & platforms.
Copy link to clipboard
Copied
Responsive does seem to be what Adobe is pushing for everyone to use.
Too bad really, because while it's getting better, certain aspects of it require a doctorate in CSS3 and HTML in order to successfully customize it.
Cheers... Rick
Copy link to clipboard
Copied
Thanks.
It is difficult for me to get a doctorate in CSS3 and HTML5 (lol).
To be honest, I'm fed up that something bad happens to WebHelp on every OS and browser upgrades. (I guess it is the same for Adobe.)
One of our mistakes is that we put WebHelp on local drive and make users browse it. WebHelp should be browsed over IP network. The Web technology is exist for the Web.
And more than anything, its pace of change is too fast.
I think PDF is an appropriate method to transmit the information to users also in the future.
PDF? I do not like it, but it is reliable, safe and useful way in fact.
Because PDF has been standardized as ISO standards, the backward compatibility is guaranteed.
In addition, Adobe Reader is unnecessary to view PDF now.
Most of the famous Web browsers can display PDF without plug-ins.
Surprisingly, in Windows 10, MS Edge browser is the default application for .pdf.
In those reasons, I think PDF is also a good solution to deliver the information to users.
I need to learn more, anyway...
Copy link to clipboard
Copied
We found that it is possible to avoid the disappearance of TOC by changing the code of whver.js that handles browser detection.
We added some lines to make Edge behave like IE.
No TOC disappearance and no other problem at the moment.
Copy link to clipboard
Copied
Thank you for posting that workaround.
See www.grainge.org for RoboHelp and Authoring tips
Copy link to clipboard
Copied
Can you let us know what lines were changed?
Copy link to clipboard
Copied
Hi Jeff.
In short, we (not professional programmers) just made a branch for MS Edge.
We've added the following eight lines to the last of whver.js file.
if (navigator.appVersion.indexOf ("Edge /")! = -1)
{
gbIE = true;
gbIE4 = true;
gbIE5 = true;
gbIE55 = true;
gbIE10 = true;
}
As a result, WebHelp behave like for IE when detecting the user agent of MS Edge.
Repeatedly to say, we are amateurs at programming.
We asked to check this file to Adobe, but there is no reply. (as usual)
Is there any professional JavaScript programmer?
Is this a good way?
Keita