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

Side by Side Diff: LayoutTests/http/tests/security/isolatedWorld/events-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 unified diff | Download patch
OLDNEW
1 CONSOLE ERROR: XMLHttpRequest cannot load http://127.0.0.1:8000/security/isolate dWorld/anyfile. No 'Access-Control-Allow-Origin' header is present on the reques ted resource. Origin 'http://localhost:8000' is therefore not allowed access. Th e response had HTTP status code 404. 1 CONSOLE ERROR: XMLHttpRequest cannot load http://127.0.0.1:8000/security/isolate dWorld/anyfile. No 'Access-Control-Allow-Origin' header is present on the reques ted resource. Origin 'http://localhost:8000' is therefore not allowed access. Th e response had HTTP status code 404. Alternatively, if you want an opaque respon se, switch to The Fetch API in 'no-cors' mode.
2 2
3 3
4 Text attribute event listeners should always fire in main world: PASS 4 Text attribute event listeners should always fire in main world: PASS
5 Function attribute event listeners should fire in the world where they were crea ted: PASS 5 Function attribute event listeners should fire in the world where they were crea ted: PASS
6 XHR attribute event listeners should fire in the world where they were created: PASS 6 XHR attribute event listeners should fire in the world where they were created: PASS
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698