Support Forum

The obvious but sadly flippant answer to that is to lobby Apple to get their software to work. But we all know that would be wasted effort.

What most of our users do who have discussed this in the past is to recommend their members use a different browser that both works as standard and gives them a better browsing experience all round. Chrome, Firefox (now available for IOS) and Mercury are three that I promote, use and enjoy using.

It would be great if we could do something about it but sometimes you are just up against a brick wall where you have to hang around waiting for fixes to come along.

I know. Like I keep saying - lousy browser.
However, this has nudged us to perform another search and we have encountered one or two people who think they might have resolved it with a Safari-only workaround. So far we have not found these solutions work but it is being re-examined. If we find a workaround that does the trick then we will, of course, use it up until the time Safari starts to behave properly.

As far as Safari then no. It is the browser. Always has been behind the curve on its javaScript implementation. The one workaround we did sort of stumble across can not be applied sadly.