(No Ratings Yet)
Loading ...We took a quick look at Google’s new Chrome browser this morning. MadCap’s Flare Web based Help seems to work fine, but there seems to be a problem with RoboHelp’s Web Help – specifically the Table of Contents.
We dragged some old RoboHelp 5 generated Web Help files into the browser, and we looked at some of the examples listed on Adobe’s Web site (http://www.adobe.com/products/robohelp/customer_examples/). We haven’t had a chance to do any further testing.
Update – The problem is also there with RoboHelp 6 generated Web-based Help.
We suspect it is a JavaScript with Frames issue. The “Section 508″ (non-JavaScript) version displays without any problems.
{ 6 comments… read them below or add one }
It does appear that with Flare that context senstive calls will work also.
Google would cross all the web records haha
Jon Galvin has given his thoughts on why Google has create Chrome
http://www.suncao.com/google-gets-the-last-piece-of-the-puzzle
I’m using RoboHelp HTML v7 and there is no TOC, Glossary, or Index, and Search does not work. Basically doesn’t work with frames.
At the Online UA Conference Europe 2008, Adobe’s speaker said this problem could be fixed simply by adding a single line of code to Help (HTML) file. He didn’t state what that line of code was, unfortunately.
It’s the whvers.js that needs to be amended, apparently.