I'm having the same issue... works fine on a MAC in Mozilla, but as soon as you go to Safari, you get a 404 error on the right pane. The code we are using is as follows:
I'm using WebHelp and this is only happening in context sensitive help. It kind of looks like it doesn't like the # that robohelp puts in front of the ID... though that doesn't make a lot of sense. We're also noticing that whtbar.js is throwing an error on line 1356 when looking at the Safari log.
Suggestions? Ideas... if I don't find a way to fix this by Monday then it looks like our entire help system is going back to JSP :( :( :( :( :( :( ....nooooooooooooo
I'm very curious to know if anyone has resolved this issue. My group is currently shopping for a new help application and the problem with non-functional context links in Safari is the biggest shortcoming with our current app.
Does anyone know if help systems produced by RoboHelp 7 can supply working context links in Safari?
Sad to say, being compliant with W3C does not ensure everything will work the same way across platforms. Safari does not respond to several techniques written for Windows.
You may not find this acceptable, but here's a thought: Switch to Firefox to run WebHelp in Mac OS. You may still have some incompatibilities, but less so in Firefox, I believe.
Our software is compliant 100% on Safari and it would not please the powers that be if only the help is not compliant and therefore we have to take this supported browser off our list.
I bought RoboHelp because it said it was compliant, now I have to find a ways to make it work on Safari..... has ANYONE gotten it to work? :(
We still have the problem that safari cannot cope with the angle brackets that follow the #:
is getting encoded ( index.html#%3Cid=2%3E%3Ejava=true).
Maybe there is a solution by now?
Not knowing anything about this technique for calling help, I ask this dumb question:
Does the syntax require the double >> before java?
We are using RH 5x, generating WebHelp, and are just now trying to be browser-compliant with Safari/Mac. We have this exact issue.
Has anyone solved it?
Does anyone know if it is fixed in RH7?
Did you ever get this resolved? I have been battling with sarafi for quite some time. My boss wants me to tell him if the update to 8 will fix it before we purchase. I have a license for webworks but do not want to covert all to framemarker.