Skip to main content
C
ChristineWeldrick
January 13, 2026
Question

Responsive HTML5 WebHelp search: “Previous” pagination updates count but not results

  • January 13, 2026
  • 6 replies
  • 215 views

Hi RoboHelp team,

We are seeing a reproducible issue with Responsive HTML5 WebHelp search pagination where the Previous (<) button updates the footer count but does not re-render the results list.

Steps to reproduce

Open Responsive HTML5 WebHelp output

  1. Search for a term with more than one page of results (e.g. vegetation)

  2. Scroll to the bottom of the results

  3. Click Next (>) → results correctly advance (e.g. items 21–25)

  4. Click Previous (<)

Observed behaviour

  • The footer updates correctly (e.g. “1–20 of 25 results”)

  • The results list does not update and still shows the later-page items (stale DOM)

Expected behaviour

  • Clicking Previous should re-render the correct earlier page of results, matching the footer and page state.

Environment

  • Adobe RoboHelp (2020)

  • Output: Responsive HTML5

  • Skin: Azure Blue

  • Issue reproducible across multiple published builds

  • CHM output not affected

We attempted multiple JavaScript-based workarounds (forcing navigation, reloads, DOM clearing via master page), but the issue persists in published output, suggesting the search UI is reusing cached result elements rather than repainting on backward pagination.

Is this a known issue or limitation in Responsive HTML5 search pagination?
If so, is there an official fix or recommended workaround?

Thanks for your help.

6 replies

Peter Grainge
Community Expert
Peter GraingeCommunity Expert
Community Expert
January 20, 2026

Whoah! Jenkins WebHelp is an automated system and you are talking about frameless.

 

If you generate a responsive output with a new Azure Blue template to your hard drive (thus not using Jenkins) , do you then get the new search I showed you? If you do, then any issues beyond that are Jenkins related and not something this forum can help with.

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

 

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Peter Grainge
Community Expert
Peter GraingeCommunity Expert
Community Expert
January 16, 2026

I think you have missed the point. The issue was fixed in 2020 by changing how the search works, as I have shown in the screenshot with the search in a sidebar. That is how they fixed it and there only the number of results are shown.

 

What I don't understand is you say you created a new skin and see the same old skin. That is why I asked if you had selected the new skin in the preset. You will only see the search in the sidebar with a new skin, not a duplicate.

 

Your options to find the bug are:

 

Let me know how you get on.

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

 

 

 

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
C
ChristineWeldrickAuthor
January 20, 2026

Hi Peter, thanks — that makes sense now and I think we’ve aligned.

I can confirm the issue is reproducible in our production output (built via a Jenkins_WebHelp preset). That preset is currently using the older frameless WebHelp skin (EV_Webhelp/frameless.skn), and the pagination bug occurs there (Previous updates the footer/page count but the results list does not re-render).

My earlier “successful” testing was done using the Responsive HTML5 output preset locally with a newly created Azure_Blue variant (sidebar-style search), which does avoid the issue — but that isn’t what our published WebHelp is currently built from.

Next step on our side is to evaluate switching Jenkins_WebHelp to the newer sidebar-style search skin variant (if it’s compatible with our existing layout), otherwise we’ll escalate to Adobe Support as a RoboHelp 2020 limitation.

Thanks again for pointing out that the fix is essentially the newer search behaviour/UI. And thank you for the links.

Jeff_Coatsworth
Community Expert
Jeff_CoatsworthCommunity Expert
Community Expert
January 20, 2026

Yup - there's your issue - your Jenkins script is using an outdated preset. You need to update that.

Peter Grainge
Community Expert
Peter GraingeCommunity Expert
Community Expert
January 14, 2026

In 2020 Update 8, I just created a new Azure Blue skin and I see the search working this way.

 

image.png

 

In the Preset, did you select the new template you created?

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

 

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
C
ChristineWeldrickAuthor
January 16, 2026

Thanks so much for your replies.

 

Confirmed: the Responsive HTML5 preset is using Master Page = New Echoview Master Page and Skin = Azure_Blue. 

The issue still reproduces in published output: Next updates correctly, Previous updates the range but the result list remains stale.
Is there a way to confirm whether this is a known limitation/bug in RoboHelp 2020 Azure Blue search UI, and whether it is only resolved in RoboHelp 2022+?

Peter Grainge
Community Expert
Peter GraingeCommunity Expert
Community Expert
January 14, 2026

A bell is ringing that it was a known issue. It appears to have been fixed by changing how the results appear, see the image below. As you have all the updates for 2020 and have tried a new template, it must be a 2022 fix.

 

image.png

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

 

 

 

 

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
C
ChristineWeldrickAuthor
January 13, 2026

Thanks for the response.

I’ve added inline screenshots below showing the issue:

  • Page 1 of search results displays correctly

  • Page 2 of search results displays correctly

  • Clicking Previous (<) updates the footer count but the results list remains on the later page (stale DOM)

As shown, clicking Next (>) correctly advances the search results, but clicking Previous (<) only updates the footer range (e.g. “1–20 of 25”) while the results list itself remains on the later page (stale DOM items).

RoboHelp version:
Adobe RoboHelp Version 2020.8.34

I have all updates applied for this version. I’ve also tested with a newly created Azure Blue skin (new name, default settings), and the behaviour is the same.

I understand behaviour may differ in RoboHelp 2022.x; however, this issue is reproducible in Responsive HTML5 output in 2020.8.34.

Can you confirm whether this is a known issue or limitation in this version of RoboHelp’s Responsive HTML5 search pagination?

Peter Grainge
Community Expert
Peter GraingeCommunity Expert
Community Expert
January 13, 2026

There is a forum bug at the moment meaning attachments do not show but please use the photo icon to insert images within the post. Seeing an image inline with the text makes it easier for anyone answering or viewing the post. Please Reply to  your post and add the images in the post using the photo icon.

 

Using the Azure Blue skin in 2022.6 I am not seeing a count that changes. Do you have all the updates applied? Go to the Help menu and let us have your full version number.

 

Also try adding a new Azure Blue skin giving it a different name, add a number. Does that have the count? Maybe it's something that got dropped.

 

I'm also not seeing a count from 2019. I can't access 2020 right now.

 

Are you aware your subscription entitles you to update to 2022 at no extra cost?

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

 

 

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices