Apologies, it may be our own issue after all.
Hi,
I have been experiencing the same issues on the Safari browser (v5.1.7). Are there any solutions for this issue? Thanks!
William