Skip to main content
F
Freespirit-ST
Known Participant
January 4, 2019
Answered

Index Filter Not Working in Responsive HTML5 Output

  • January 4, 2019
  • 2 replies
  • 2984 views

I am using Robohelp 2017 with 2nd update.  This help system is VERY large, and the Index has several thousand keywords and subkeywords. We have been using WebHelp output that is called by our application web server for context-sensitive help for many years now.  However the TOC was not working in Chrome, and we need to support both IE 11 and Chrome for our applications. So we just switched to Responsive HTML5, with Azure_Blue layout.  So now, our TOC and Search are working, but Index is not working. Note that Index worked fine with WebHelp – we just switched to Responsive HTML5 because of the TOC issue. Our layout is set up so you click to view in full context (with the TOC, Index, and Search panels).

From other Forum threads here with related issues, we applied the updates to the JS files for Search, and that helped.  I looked for any other possible updates we needed – except for going to RH 2019! – and I think we are up-to-date.

Here’s the issue with our Index in Responsive HTML5, in  both IE11 and Chrome browsers:

  • The Index initially displays the first portion of the Index.  I can scroll down to the bottom of the Index panel to go further down, and vertical scroll bar pops back up a bit so that I can continue to scroll further down. That happens at least some of the time! So, it is not a smooth scroll to go through the entire humongous Index, if at all. Because of the size of the Index, I’m not sure if we can do anything for this.
  • If I enter a keyword into the Index Filter Keywords field at the top, then press Enter – nothing happens. If I don’t press Enter, nothing happens. My coworker is able to use the Index filter, some of the time.  For me, it just sits there. Because our Index is so very big, we really would like the Index filter feature to work.

We need to know whether this could be an issue or limitation of Responsive HTML5 output. We would like to continue using this, since it fixed our TOC problem in Chrome. But maybe a different layout would work better with such a large help system. Or maybe there is a RoboHelp setting or option that we missed. Or - would going to Robohelp 2019 help us with this Index issue with specific fixes??

Any suggestions and answers are greatly appreciated.  We love our Index and want it to work.

Thanks.

Susan

This topic has been closed for replies.
Correct answer Jeff_Coatsworth

Couple of suggestions - try as an experiment - to create the same help using other layouts & see if you get the same effect or not. Also try out the sample projects & see if they demonstrate the same behaviour too. That might give you a clue as to if it's the project, the layout used or the version of the software.

2 replies

J
JGaf10311788
Inspiring
October 21, 2019

thank you for posting this! 

 

 

Jeff_Coatsworth
Community Expert
Jeff_CoatsworthCommunity ExpertCorrect answer
Community Expert
January 4, 2019

Couple of suggestions - try as an experiment - to create the same help using other layouts & see if you get the same effect or not. Also try out the sample projects & see if they demonstrate the same behaviour too. That might give you a clue as to if it's the project, the layout used or the version of the software.

    F
    Freespirit-STAuthor
    Known Participant
    January 4, 2019

    Thank you!  Do you mean other layouts for Responsive HTML5?  We will do that.

    I did forget to say that I have several other much smaller help systems, and they have NO problems with our Responsive HTML5 layout. But index is much, much smaller. All navigation features work just fine.

    I appreciate your response, Jeff - we will continue to experiment.

    Susan

    Jeff_Coatsworth
    Community Expert
    Jeff_CoatsworthCommunity Expert
    Community Expert
    January 4, 2019

    Yes, other HTML5 designs - it could be that you find that the enormous size of the index just bogs down in the loading. I've seen that with WebHelp indices and TOCs that were the product of merged projects.

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