It turns out that Safari 2.0.4 does not throw an exception when an XHR violates the same-origin policy.  As a matter of fact, it appears to do nothing.  The test will no longer fail if an XHR on a Safari browser fails to generate a same-origin policy violation.

Review by: jgw (desk check)

git-svn-id: https://google-web-toolkit.googlecode.com/svn/trunk@2003 8db76d5a-ed1c-0410-87a9-c151d255dfc7
1 file changed