I recently noticed that my HTML5 output wasn't working on iPhone, iPad, and macOS Safari.
First I thought something was wrong with my own scripts, but after some digging, I found that it's a bug in the native RH JS files.
That means that none of your HTML5 RoboHelp projects will work properly on current iPhones, iPads, and Macs (= devices running iOS 10 or macOS Sierra).
This is a major bug that should be addressed as soon as possible. The bug has already been filed by Alexandra Duffy one month ago, but it is still "Unverified": Bug#4192629 - Safari 10 update has caused HTML5 Help from RH to stop working.
Luckily enough, Edward Doris has already posted a bugfix in the above bug report. It seems to solve the problem on all devices. However, implementing the bugfix requires advanced JS knowledge.
Please provide an official bugfix as soon as possible.
Use the Bugbase to log it as a bug yourself - that gets it on Adobe's official radar.
I think what Jeff may be hinting at here is that if you add another report of the bug you noted, it will aid in stressing to Adobe that it's a higher priority bug than one that may simply be some cosmetic issue or other issue that doesn't manifest often or easily.
And in the event you are unaware of how to file such a bug, you click the link below and complete the form:
It's already logged there. I think it's better to use the "vote" feature on the existing bug report than to create duplicate entries.
I only posted this here to let the community know, as it affects all HTML5 projects. Might save you time – I spent several hours in search for a solution.
Out of curiosity, when you say ALL HTML5 projects (assuming you meant outputs here) are you meaning both the Responsive HTML 5 as well as the Multiscreen HTML 5?
Yes, I meant outputs. To me, the whole thing is a project, but you're right, we should stick to RoboHelp terminology 🙂
I didn't test Multiscreen HTML5. But I think it's very likely that Multiscreen is broken as well. If you want to know for sure, it's very easy to find out – simply create a dummy project, upload it to a server, open it on a Mac (running macOS Sierra) or an iPhone/iPad (running iOS 10) and check if the topic content is displayed.
Bug is still "Unverified", so I guess it will not be fixed anytime soon.
I created a modified version of rh.min.js that you can use as a workaround. It includes the bugfix posted by Edward.
1. Download the file
2. Copy it to the \template\scripts subdirectory of your RoboHelp output directory (not the project directory).
Note that the file will be overwritten every time you re-generate your content.
I just had this reported to me about 2 hours ago.
When using Safari 10.0.1 to view a Resp. HTML 5 help system, the help opens but no content displays until you refresh the browser.
Yes, I added a vote to the bug reported by Alexandra Duffy that is cited above.
Update: I recompiled the project, then copied the updated .js file into a network directory, my co-worker tried it out and reported it didn't work.
Same here. Cannot get responsive HTML5 to work in Safari 10.0.1. I have tried Edward Doris' fix (in original post) but cannot find the code he is referring to. Has anyone found a fix for this until Adobe fixes it?
We are working on a fix with utmost priority. Patch will be available shortly.
This issue is fixed now.
The update is available through Adobe Update Manager (AUM): Please check for the updates in RoboHelp’s menu > File > Updates.
I don't have a File > Updates option. Can you provide a direct link?
Try Help > Updates
Per Help > About RoboHelp, I'm on version 126.96.36.1994. When I ran the Updates option, it said I was up-to-date, but I've not been prompted to go through any installation this AM.
Update: I just looked here: Search Results for “RoboHelp (2015 Release)” – TechComm Central by Adobe and it's not listed yet.
Looks like they rolled back the 2015.0.4 patch - I suspect they're trying to reformulate the .0.4 patch to include this fix before they repost it again.
The fix for this issue is now available in the latest update. Please download and install the latest update.
I went to lunch, came back, and using Help > Updates doesn't trigger the automatic update. I checked this page - Search Results for “RoboHelp (2015 Release)” – TechComm Central by Adobe - and didn't see it - is that not where I should be looking?
Try File > Help > Updates - that seems to be the RH2015 spot within the software.
This is frustrating me.
From here - RoboHelp (2015 Release) Update 4 released – TechComm Central by Adobe - which is where I ended up when I searched for "Robohelp 2015" - there is information about 2015.0.4. Within that page, there is a link to Adobe - Support : RoboHelp Support Center : Service Releases - which is the page Jeff linked to above but, like Jeff said, 2015.0.4 isn't listed.
I wouldn't be as frustrated if there were two posts by Adobe Support in this thread saying that the update is available when, clearly from central Iowa, the update is not available... Sigh.
Post #9 over on this thread - Filter icon is displayed without using filters - seems to imply that the updater is working today; but I have seen posts in the forums complaining about disabled Updaters due to corporate firewalls (which is why I maintain a bookmark to the downloads page).
If it wasn't sad, it'd be hilarious.
Today, on Nov 4, 2016 @ 6:56 AM, Adobe posted the update was available.
Then, today, on Nov 4, 2016 @ 9:13 AM, Adobe posted the update was available.
Today, as I shut down my PC for the day, at Nov 4, 2016 @ 3:55 PM, it has not been posted.
Maybe by Monday...
Apologies for the inconvenience caused.
The update is available through Update manager for now. Website update usually takes time. Since this issue was critical and an immediate fix was required, we communicated it's availability through update manager. Please go to FIle > Help > Updates.
Please let us know in case you see issues.
Is this the updated version?
Not sure if 188.8.131.524 sets the newest one - that level was reported by Adobe TCS as being for the 12.0.4 patch & I'm not sure if the release level changed with this new 184.108.40.206 fix.