GitLab

With out-of-blink CORS, CORS errors for XHR are displayed in
ResourceLoader, which brings flakiness to open-in-body-* tests, because
Resource and ResourceLoader continue working a while after
ThreadableLoader::Cancel is called, because of the async cancellation
mechanism in ResourceLoader. These tests make ill cross-origin requests,
and then abort them (by calling open() of the same XMLHttpRequest
object) after that. When a response arrives befor the cancellation is
performed but after async cancellation is started, then we see a
console log of a CORS error for an aborted XHR.

Let's have such tests use testharness.js instead of js-test.js so that
such console errors don't affect the test results.

Bug: 736308
Change-Id: I680ce2997a6c10e06368db8a89d789534c47097d
Reviewed-on: https://chromium-review.googlesource.com/1156329
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#580035}