Safari has always been more scrupulous about honoring various security features/standards in HTML and/or Javascript than other browsers so the difference in Safari and Firefox or Chrome would not be surprising. The fact Safari is not having the problem on other financial web sites would seem to indicate the issue resides in the particular web site. If one had the inclination, some hours spent in close scrutiny of the code from that site might reveal what is triggering the timeout. Personally I would look first at the Javascript used.
If you can find a link to contact the site webmaster you might inform them of the issue. It is highly likely they do not know it exists. Sadly it may be equally likely they do not care and work under the assumption that everyone uses Internet Explorer. (Here it is Sunday, the first day of the week and I have already gotten my weekly Microsoft Internet Exploder grumble off my chest. — What
am I to do for the rest of the week?
)
