the first script error is
My sample projects are stored on my user profile, which is located on a network share (which explains the glacial slowness in loading RoboHelp mistakes 101!!). Have now moved that to the c: drive to speed things up!
I do have local admin, and I've now activated those 2 options in the IE Advanced settings. This has resolved the issue with the dropdown hotspot failing to open.
The other error messages when RH first loads a project in.. having read the jquery forum linked above https://forum.jquery.com/topic/jquery-2-1-1-min-js-object-does… I suspect that these issues are down to incompatibility between legacy IE and the v2 jquery used within RH2017.
I have a "cunning plan" to replace the contents of "C:\Program Files (x86)\Adobe\Adobe RoboHelp 2017\RoboHTML\plover\lib\jquery-2.1.1\jquery-2.1.1.min.js" with the contents of a jquery v1 library instead. If that stops the errors then it'll confirm my suspicions - but what other issues this might cause are to be discovered!! And any future RH patch/update would most likely restore the original file anyway..
I can't say this is really a good idea, but "force-downgrading" to Jquery 1.12.4 (by overwriting the js file with the contents of the older version) clears the first error message. But this could cause any number of other issues during usage!
Then I hit the 2nd error, which points at angular.js v1.3.16. A quick google confirms that Angular depreciated support for legacy IE after v1.2. So the same issue...
The 3rd error points at a file called "review_comments.min.js" which appears to utilize angular js, so is related to the 2nd one.
I'm not going to attempt any further "fixes" as this isn't sustainable, and our IT policy certainly wouldn't allow me to deploy the same thing to other users within the company.
There are plans afoot to upgrade our browsers across the estate, so may just have to hold off on RH17 until we can get all users upto at least IE11/Chrome 60. Good old RH8 is still doing the job!
I spoke to Adobe Tech Support today and they provided an updated "project.dll" which has resolved the errors. He indicated this would be rolled out in a future RH update.
This was the same for my case also, the revised project.dll Adobe provided seems to have resolved it.