Search engine does not return results in IE for Responsive HTML5 help

48 replies
4556 views
Translate

I'm using RoboHelp 2017 to generate responsive HTML5 help. I noticed that, while the search function works for both Chrome and Firefox, it does not work when the help is opened in IE 11. I tried this from both a web server and a file server with the same results. I experimented a bit with the search settings in RoboHelp but to no avail. RoboHelp 2017 is up-to-date with patches. Has anyone else seen this issue (and found a solution)?

HTML5 layout

This topic is closed to new replies. Start a new post to keep the conversation going.

Peter GraingeCorrect answer

Community Expert

Hi,

I have tried that but its still the same.. using 2017.

I imported the latest .slz for the Indigo from the Robohelp website.

Returns search results in chrome instantly whilst ie11 just hangs with the search box going round and round.

OK. In that case, I think the files attached to the bug report below will fix the problem for you.

Tracker

See www.grainge.org for RoboHelp and Authoring information

@petergrainge

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

C

CaitlynJohnston

Inspiring

I'm having this issue now, too, where in IE11, the Search feature doesn't work. It's been 4 months. Has anyone heard when this bug will actually be fixed and released?

Translate

Jeff_Coatsworth

Community Expert

Did you try the fixes in the Tracker item?

Translate

Peter Grainge

Community Expert

Jeff. They will work but the files on my site are from Adobe and it will be

cleaner when Adobe issue them officially.

Translate

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

E

ENTRGWHAuthor

Known Participant

I put them here:

C:\Program Files (x86)\Adobe\Adobe RoboHelp 2017\RoboHTML\ResponsiveHelpExt\widgets\common\scripts

Translate

raylangivens

Known Participant

ENTRGWH - thank you! Now that this discussion has complete information, other folks who run into this issue will be able to fix it quickly. Do you happen to know if Adobe plans to fix this? IMO, it's a big deal.

Translate