Skip to main content
A
Anonymous
September 3, 2008
Answered

WebHelp in Chrome - first look

  • September 3, 2008
  • 29 replies
  • 9060 views
Just downloaded the new Chrome browser from Google, and as I feared, my WebHelp doesn't work (nav pane contents don't display). I am using a skin.

I tried a test project using the default skin and found that only pure html works for navigation pane format (WebHelp Options page 3).
If I use DHTML > Pure HTML the pane comes up empty
If I use Java Applet > Pure HTML I get a message in the pane saying no plugin is available to display the content. The odd thing is that I included some drop-down text (which is javascript, right?) and that woks fine.

Pure html is ok, except there's no Search Input field available. So, I'd love to be able to use dhtml or Java for the nav pane.

If anyone has an idea for getting this to work I'd be grateful for info.

Jeanne
This topic has been closed for replies.
Correct answer vivek_k-GfmzA1
Hi,

Adobe has been working on it and if you do the following changes to your file whvers.js in C:\Program Files\Adobe\Adobe RoboHelp 8\RoboHTML\WebHelp5Ext\template_stock folder.

Add following 2 lines at the top along with other variable declarations.
var gbChrome = false ;
var gbChrome=(gAgent.indexOf("chrome")!=-1);

and then add a condition
if (gbChrome)
{
gbSafari = true ;
gbSafari3=true;
}

This should fix TOC/Index/Glossary/Search loading issues.
I am attaching code from fixed whvers.js file as well.

Please report if you find more issues with Chrome as we are actively trying to fix them.

thanks,
Vivek.
Adobe RoboHelp Team.

29 replies

Show previous replies
Peter Grainge
Community Expert
Peter GraingeCommunity Expert
Community Expert
September 12, 2008
If anyone prefers to download whver.js instead of amending the code, see Snippet 103 on my site.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
V
vivek_k-GfmzA1
Participating Frequently
September 13, 2008
Hi Leon,

Fixing just whver.js in X5.0.2 will not work. As I posted earlier we have done many fixes for Safari browser in RH7, they also need to be brought in for X5 to work properly in Chrome.

Vivek.
MergeThis
MergeThis
Inspiring
September 15, 2008
Vivek, I assume that you'll make an announcement when that happens (complete Safari/Chrome fixes for X5.0.2)?

Thx,
Leon
Peter Grainge
Community Expert
Peter GraingeCommunity Expert
Community Expert
September 12, 2008
meKarla

I took a look at that article and there is more than one thing that is wrong. For example, it states RH does not output to PDF! It also makes a big thing of the ability to email topics for review. Doesn't mention as I read somewhere else that it is one topic at a time. One of my projects has 12,000 topics. I think I will pass on that method!

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
M
meKarla
Inspiring
September 12, 2008
yep, I have 9 different projects, but the biggest is only just under 500 topics, but I don't think my SMEs want 500 emails to review. It's hard enough to get them to review a Word doc.
Peter Grainge
Community Expert
Peter GraingeCommunity Expert
Community Expert
September 12, 2008
I cannot comment on inclusion in updates.

I will be putting a copy of the amended whvers.js on my site over the weekend. Look in Snippets.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
M
meKarla
Inspiring
September 12, 2008
on my box the file is called "whver.js"
V
vivek_k-GfmzA1
Participating Frequently
September 12, 2008
Hi Betsy,

For now one has to fix whvers.js manually. It will be included in any update we have in future. Chrome is a beta version right now, claiming support for it is risky.

You please download RH7 trial version and apply the 7.01 and 7.02 patches and see if it solves all your issues on Safari and Chrome. If you still have issues then please let us know.

thanks,
Vivek.
Adobe Systems.
A
Anonymous
September 11, 2008
Thanks, Vivek,

Does that mean if we upgrade from RH5 to RH7 and then update our whvers.js, our navigation and search should work with both Safari and Chrome?

Also, will the revised whvers.js file be included in a free software update for RH7 soon (making a manual update to the file unnecessary)?

Thanks again,
Betsy
A
Anonymous
September 10, 2008
Vivek,

I'm using RoboHelp 5. My project has a whver.js file (not whvers.js), and I updated the code with the revised that you posted. However, my navigation and search are still not showing up. I was wondering if you had any suggestions for getting the navigation to work for legacy RoboHelp users.

Thanks,
Betsy
V
vivek_k-GfmzA1
Participating Frequently
September 11, 2008
Hi Betsy,

Chrome is using WebKit engine which is same as what Safari uses. We had fixed many Safari issues in RH7 and current fix for Chrome just involved recognizing that browser and mapping that to same as Safari.
In order to support Chrome in X5 we need to bring in all these fixes which will be difficult to do.

thanks,
Vivek.
M
meKarla
Inspiring
September 10, 2008
I did notice that at least one of the things that MadCap pointed out was not true, so one wonders what else isn't true (or which version they used as comparison).

I created a new index, told RH to generate with that index, and deleted the old index. The offending text in the Index was still there. I have since done a search of topics, and found that the offending text was added to the meta tags in several topics (e.g., <META NAME="MS-HKWD" CONTENT="BadText">) and removed it. I'm regenerating now to see if that fixed it.

*Most* of the time, when I find RH stupidness, I can find a workaround or fix (often with tips from other RH users and gurus--thank you, thank you, thank you!). But I've worked with numerous technical writers who were not very technical (and some barely writers) who would not be able to fix it, and would likely have convulsions at the mere thought of editing the .js files.

Sometimes RH does things for me, because it thinks it knows better (and sometimes it does know better). For example, some of the projects that I am working on were started 4 or 5 years ago by someone else on RHX5. While manually editing the help to "fix" the tags, I would occasionally miss a closing tag. Rather than highlighting the leftover tag (as Front Page does), RH would say, "Oh, what you meant to do is make everything bold!" So then I would have to go edit the HTML again (more carefully this time) to get rid of all the bold tags.

I used to use DocToHelp 2000 to create printed docs, then generated JavaHelp from them, then had to spend a few weeks editing the individual html files. RH causes many fewer headaches for me than DocToHelp ever did, but I don't do JavaHelp here. And version 7 is MUCH improved over the previous versions. Let's hope Adobe continues with its awesome support and continues to make improvements!
Peter Grainge
Community Expert
Peter GraingeCommunity Expert
Community Expert
September 10, 2008
My point was more not to worry unduly about what you read in the comparison.

If it is the default, it cannot be deleted. Otherwise it shouldn't be a problem. Haven't seen anyone post about it.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
M
meKarla
Inspiring
September 10, 2008
Yes, Peter, as Jeanne said, it was awesome and speedy response.

I'm dealing with other issues now, in which my Index, which I deleted, refuses to go away.
Peter Grainge
Community Expert
Peter GraingeCommunity Expert
Community Expert
September 10, 2008
meKarla

I hope you will acknowledge the speedy response this got. Looking at that article on MadCap's site, it is rather exagerated in places and wrong in others. It also does not mention some deficiencies in the other direction but I don't believe in tool wars. A good product can stand on its own two feet.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
M
meKarla
Inspiring
September 9, 2008
YAY, Leon!! That's what it was. When I regenerated WebHelp with "Plain HTML" (the third page), the TOC reappears. The Index and Search also appear now, but look b-- ugly. (This is the way it's "supposed" to look: http://help.globalscape.com/help/eft5/) So now, if I want to spend more time on it, I have to figure out how to make the plain html Index and Search panes more attractive. Or just move on...

Thank you!
Karla
V
vivek_k-GfmzA1Correct answer
Participating Frequently
September 10, 2008
Hi,

Adobe has been working on it and if you do the following changes to your file whvers.js in C:\Program Files\Adobe\Adobe RoboHelp 8\RoboHTML\WebHelp5Ext\template_stock folder.

Add following 2 lines at the top along with other variable declarations.
var gbChrome = false ;
var gbChrome=(gAgent.indexOf("chrome")!=-1);

and then add a condition
if (gbChrome)
{
gbSafari = true ;
gbSafari3=true;
}

This should fix TOC/Index/Glossary/Search loading issues.
I am attaching code from fixed whvers.js file as well.

Please report if you find more issues with Chrome as we are actively trying to fix them.

thanks,
Vivek.
Adobe RoboHelp Team.
V
vivek_k-GfmzA1
Participating Frequently
September 10, 2008
Correct path is "C:\Program Files\Adobe\Adobe RoboHelp 7\RoboHTML\WebHelp5Ext\template_stock folder"

Thanks Jeanne for pointing it out.

Vivek.
Show more replies
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices