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

Unified Diff: trunk/LayoutTests/http/tests/w3c/webperf/submission/Intel/resource-timing/test_resource_timing_cross_origin_redirect_chain-expected.txt

Issue 16603005: Revert 152077 "[Resource Timing] Expose redirect timing information" (Closed) Base URL: svn://svn.chromium.org/blink/
Patch Set: Created 7 years, 6 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: trunk/LayoutTests/http/tests/w3c/webperf/submission/Intel/resource-timing/test_resource_timing_cross_origin_redirect_chain-expected.txt
===================================================================
--- trunk/LayoutTests/http/tests/w3c/webperf/submission/Intel/resource-timing/test_resource_timing_cross_origin_redirect_chain-expected.txt (revision 152082)
+++ trunk/LayoutTests/http/tests/w3c/webperf/submission/Intel/resource-timing/test_resource_timing_cross_origin_redirect_chain-expected.txt (working copy)
@@ -1,13 +0,0 @@
-Description
-
-This test validates the values in resource timing for cross-origin redirect chain.
-
-
-
-PASS window.performance is defined
-PASS Starting document.location.hostname is correct (127.0.0.1:8000)
-PASS redirectStart should be 0 in cross-origin redirect!
-PASS redirectEnd should be 0 in cross-origin redirect!
-PASS fetchStart should be 3 secs later than navigationStart
-PASS startTime should be the same to fetchStart in cross-origin redirect!
-

Powered by Google App Engine
This is Rietveld 408576698