| commit | dd653217e511b08de2f10504761547da430ff2b5 | [log] [tgz] |
|---|---|---|
| author | gwt.team.mmendez <gwt.team.mmendez@8db76d5a-ed1c-0410-87a9-c151d255dfc7> | Wed Mar 05 15:47:36 2008 +0000 |
| committer | gwt.team.mmendez <gwt.team.mmendez@8db76d5a-ed1c-0410-87a9-c151d255dfc7> | Wed Mar 05 15:47:36 2008 +0000 |
| tree | c83177ec54193f543be151ed9d04f257dff527e4 | |
| parent | 890cb21d7d0545f97c3ca2e27536ec65e64ac313 [diff] |
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