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

Side by Side Diff: LayoutTests/http/tests/appcache/remove-cache-expected.txt

Issue 1018903002: Show deprecation warnings for header values in XHR according to RFC 7230 (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master
Patch Set: Created 5 years, 3 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 WARNING: Synchronous XMLHttpRequest on the main thread is deprecated bec ause of its detrimental effects to the end user's experience. For more help, che ck http://xhr.spec.whatwg.org/. 1 CONSOLE WARNING: Synchronous XMLHttpRequest on the main thread is deprecated bec ause of its detrimental effects to the end user's experience. For more help, che ck http://xhr.spec.whatwg.org/.
2 CONSOLE WARNING: Synchronous XMLHttpRequest on the main thread is deprecated bec ause of its detrimental effects to the end user's experience. For more help, che ck http://xhr.spec.whatwg.org/. 2 CONSOLE WARNING: Synchronous XMLHttpRequest on the main thread is deprecated bec ause of its detrimental effects to the end user's experience. For more help, che ck http://xhr.spec.whatwg.org/.
3 CONSOLE WARNING: isValidHTTPHeaderValue() will be deprecated and will be removed in future.
3 Test that a 404 response for manifest results in cache removal. 4 Test that a 404 response for manifest results in cache removal.
4 5
5 Frame 1: Manifest is still available, so a new master resource is added to the c ache. 6 Frame 1: Manifest is still available, so a new master resource is added to the c ache.
6 Frame 2: Manifest loading results in 404 response, so the cache group becomes ob solete, and an obsolete event is dispatched (because the document in frame was a ssociated with a cache in the group). 7 Frame 2: Manifest loading results in 404 response, so the cache group becomes ob solete, and an obsolete event is dispatched (because the document in frame was a ssociated with a cache in the group).
7 Frame 3: Manifest is still 404 - the document is never associated with a cache. 8 Frame 3: Manifest is still 404 - the document is never associated with a cache.
8 Frame 4: Manifest is now available, so the document gets associated with a cache in a newly created group; the obsolete cache group is not affected. 9 Frame 4: Manifest is now available, so the document gets associated with a cache in a newly created group; the obsolete cache group is not affected.
9 Should say SUCCESS: 10 Should say SUCCESS:
10 11
11 SUCCESS 12 SUCCESS
12 13
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698