diff options
| author | aa@chromium.org <aa@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-08-21 19:00:26 +0000 |
|---|---|---|
| committer | aa@chromium.org <aa@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-08-21 19:00:26 +0000 |
| commit | 20dcfd549f122b8a15b76447c14c5c3539c88242 (patch) | |
| tree | ae8c81d0906704665653f2feb104c65215af098b /webkit/activex_shim | |
| parent | e718099e5cb97a6b49788c977ef157083e12334e (diff) | |
| download | chromium_src-20dcfd549f122b8a15b76447c14c5c3539c88242.zip chromium_src-20dcfd549f122b8a15b76447c14c5c3539c88242.tar.gz chromium_src-20dcfd549f122b8a15b76447c14c5c3539c88242.tar.bz2 | |
Re-land r23931: Plumb whiteListAccessFromOrigin() through
Chromium's WebKit API and enable the related layout tests.
After some digging, I realized the problem here, sorta. The
test that was failing actually fails flakily. There are two
flavors of this test: sync and async. The async test was
already marked flakey, the sync test was not.
My change upstream refactored XHR to make the sync and async
cases share much more code. So it is not surprising that they
are now both flakey.
Review URL: http://codereview.chromium.org/173209
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@23994 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'webkit/activex_shim')
0 files changed, 0 insertions, 0 deletions