We also believe that this problem only occurs with Safari, so it would be worth trying Chrome or Firefox.
We are not likely to be able to fix either Safari or our Web Site quickly, so would suggest that anyone having this problem try one of the other browsers, or Tim's suggested workaround above.
