Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(123)

Unified Diff: LayoutTests/http/tests/security/text-track-crossorigin-expected.txt

Issue 1300083002: Add suggestion to use "no-cors" with Fetch fails CORS check. (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master
Patch Set: Patch CORS error expectation files to include message about Fetch CORS. Created 5 years, 4 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: LayoutTests/http/tests/security/text-track-crossorigin-expected.txt
diff --git a/LayoutTests/http/tests/security/text-track-crossorigin-expected.txt b/LayoutTests/http/tests/security/text-track-crossorigin-expected.txt
index fb8991e7f2c374de06d2e9aebef6367ab55af9b5..5ea9037c414423e1103c3596367833269e039de2 100644
--- a/LayoutTests/http/tests/security/text-track-crossorigin-expected.txt
+++ b/LayoutTests/http/tests/security/text-track-crossorigin-expected.txt
@@ -1,5 +1,5 @@
CONSOLE ERROR: Text track from origin 'http://localhost:8000' has been blocked from loading: Not at same origin as the document, and parent of track element does not have a 'crossorigin' attribute. Origin 'http://127.0.0.1:8000' is therefore not allowed access.
-CONSOLE ERROR: Text track from origin 'http://localhost:8000' has been blocked from loading by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://127.0.0.1:8000' is therefore not allowed access.
+CONSOLE ERROR: Text track from origin 'http://localhost:8000' has been blocked from loading by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://127.0.0.1:8000' is therefore not allowed access. Alternatively, if you want an opaque response, switch to The Fetch API in 'no-cors' mode.
Tests loading cross-domain <track>.
Loading without Access-Control-Allow-Origin header, no "crossorigin" attribute on <video>

Powered by Google App Engine
This is Rietveld 408576698