X
Tap here to go to the mobile version of the site.

Support Forum

RoboHelp TOC and Index not showing after 35.0 update

Posted

Today I was making a new RoboHelp manual for my program and when I went to test it, Firefox did an update to version 35.0 and from that point on, the Table of Contents and Index tabs produced a javascriptvoid(0) error. I reverted back to version 19.0 and it worked fine but then of course Firefox did an automatic update and now the TOC and Index are gone again.

Today I was making a new RoboHelp manual for my program and when I went to test it, Firefox did an update to version 35.0 and from that point on, the Table of Contents and Index tabs produced a javascriptvoid(0) error. I reverted back to version 19.0 and it worked fine but then of course Firefox did an automatic update and now the TOC and Index are gone again.

Additional System Details

Installed Plug-ins

  • Adobe PDF Plug-In For Firefox and Netscape 11.0.10
  • PlayNow Plugin
  • Citrix Online App Detector Plugin
  • Coupons, Inc. Coupon Printer 4.0.2.0
  • Facebook Desktop Plugin
  • GEPlugin
  • Version 5.38.6.0
  • Google Update
  • Next Generation Java Plug-in 11.25.2 for Mozilla browsers
  • Picasa plugin
  • The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.
  • Shockwave Flash 16.0 r0
  • Adobe Shockwave for Director Netscape plug-in, version 12.1.4.154
  • 5.1.30514.0
  • VLC media player Web Plugin 2.1.3
  • WildTangent Games App V2 Presence Detector
  • NPWLPG
  • iTunes Detector Plug-in

Application

  • User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0

More Information

guigs 1072 solutions 11697 answers

Looks like this is also aware in the adobe forums: https://forums.adobe.com/thread/1681699

Next steps would be to file a bug in the webcompat.com page to start the conversation as it would take both parties to work on the compatibility.

Looks like this is also aware in the adobe forums: [https://forums.adobe.com/thread/1681699] Next steps would be to file a bug in the webcompat.com page to start the conversation as it would take both parties to work on the compatibility.