We're using RoboHelp 2020.8.34, and we have thumbnails for several images. The thumbnails look and open correctly, but they won't close; clicking on the X does nothing. It happens when viewing the output locally and on the server and in Edge and Chrome. Anyone else having this issue?
It's not something I've seen reported here before. Have you made any customisations to the skin you're using?
I do have a new skin, but there are only minor color changes from the original skin. I did the output using the original skin and have the same problem. Output we did for a release back in June, which was before we upgraded to release 8, works correctly.
Which output and skin are you using? I don't have RH2020 right now but I can try to test later.
I just tested with version 2020.8.34 and can confirm this for Responsive HTML5 output. It seems to work correctly with Frameless. No error to be found in the console.
I was just hoping I would be able to update 😞
Some more details on my test: I created a new project with just one topic. Output is Responsive HTML5. No skin selected (i.e. default skin).
It is not working with any of the options for thumbnails (style or create).
Thanks for testing this and confirming the problem. For now, we are coming up with a workaround as our help needs to go out shortly.
I have created a bug for this.
It would help to post here a link to that bug report. Others can then vote for it to raise the priority.
It would do no harm to contact Support as they may have a fix, although I doubt it. See https://helpx.adobe.com/contact/enterprise-support.other.html#robohelp for your Adobe Support options. The email link email@example.com is recommended as it reaches a team dedicated to Technical Communication Suite products including RoboHelp.
My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.
Thank you for creating the bug, I just voted for it.
I have exactly the same problem, I've just voted for it, hope Adobe can fix it asap.
I am currently testing RH 2022.0.346. In this version, I do no longer have this issue. Maybe, upgrading to 2022 is an option for you, too.