Revert of Show service worker navigation preload requests in DevTools Network tab

Revert of Show service worker navigation preload requests in DevTools Network tab (patchset #9 id:460001 of https://codereview.chromium.org/2620463002/ )

Reason for revert:
Caused layout test failures.


http://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=webkit_tests&tests=http%2Ftests%2Finspector%2Fservice-workers%2Flazy-addeventlisteners.html

Original issue's description:
> Show service worker navigation preload requests in DevTools Network tab.
> 
> Demo: https://youtu.be/I-Qe_Y-xYxE
> 
> Navigation Preload requests are initiated from the browser process.
> This is different from the normal network requests which are initiated from the
> renderer process.
> 
> When the DevTools show the normal requests in the Network tab, DevTool's
> Network events (requestWillBeSent, responseReceived, loadingFinished etc) are
> dispatched via InspectorInstrumentation and InspectorNetworkAgent.
> 
> This CL introduces new DevTool's Network events (navigationPreloadSent,
> navigationPreloadResponseReceived, navigationPreloadFailed,
> navigationPreloadFinished) which are dispatched via InspectorInstrumentation and
> InspectorNetworkAgent from ServiceWorkerContextClient.
> 
> In the normal requests case, we record the request sending timestamp when the
> renderer process will send the request in InspectorNetworkAgent::
> willSendRequestInternal(). But in the navigation preload case, we record the
> timestamp in the browser process, and send it to the service worker's renderer
> process using FetchEventPreloadHandle.
> 
> 
> BUG=649558
> 
> Review-Url: https://codereview.chromium.org/2620463002
> Cr-Commit-Position: refs/heads/master@{#445630}
> Committed: https://chromium.googlesource.com/chromium/src/+/4c6b3b0f11b62e069d9d84ba99dbe94a45a5c622

TBR=falken@chromium.org,pfeldman@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=649558
Review-Url: https://codereview.chromium.org/2649923007
Cr-Commit-Position: refs/heads/master@{#445684}
Committed: https://chromium.googlesource.com/chromium/src/+/f0d113c2a563169ac97086771a3ea3a24bebd73d

[horo, 2017-01-24 08:47:12]

The CQ bit was checked by horo@chromium.org

[horo, 2017-01-24 08:47:13]

Created Revert of Show service worker navigation preload requests in DevTools
Network tab

[commit-bot: I haz the power, 2017-01-24 08:47:24]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-01-24 08:48:29]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1485247632630570, "parent_rev":
"4b273e243bf047778e36cbc948f72ae13f7934cc", "commit_rev":
"f0d113c2a563169ac97086771a3ea3a24bebd73d"}

[commit-bot: I haz the power, 2017-01-24 08:49:00]

Description was changed from

==========
Revert of Show service worker navigation preload requests in DevTools Network
tab (patchset #9 id:460001 of https://codereview.chromium.org/2620463002/ )

Reason for revert:
Caused layout test failures.


http://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=...

Original issue's description:
> Show service worker navigation preload requests in DevTools Network tab.
> 
> Demo: https://youtu.be/I-Qe_Y-xYxE
> 
> Navigation Preload requests are initiated from the browser process.
> This is different from the normal network requests which are initiated from
the
> renderer process.
> 
> When the DevTools show the normal requests in the Network tab, DevTool's
> Network events (requestWillBeSent, responseReceived, loadingFinished etc) are
> dispatched via InspectorInstrumentation and InspectorNetworkAgent.
> 
> This CL introduces new DevTool's Network events (navigationPreloadSent,
> navigationPreloadResponseReceived, navigationPreloadFailed,
> navigationPreloadFinished) which are dispatched via InspectorInstrumentation
and
> InspectorNetworkAgent from ServiceWorkerContextClient.
> 
> In the normal requests case, we record the request sending timestamp when the
> renderer process will send the request in InspectorNetworkAgent::
> willSendRequestInternal(). But in the navigation preload case, we record the
> timestamp in the browser process, and send it to the service worker's renderer
> process using FetchEventPreloadHandle.
> 
> 
> BUG=649558
> 
> Review-Url: https://codereview.chromium.org/2620463002
> Cr-Commit-Position: refs/heads/master@{#445630}
> Committed:
https://chromium.googlesource.com/chromium/src/+/4c6b3b0f11b62e069d9d84ba99db...

TBR=falken@chromium.org,pfeldman@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=649558
==========

to

==========
Revert of Show service worker navigation preload requests in DevTools Network
tab (patchset #9 id:460001 of https://codereview.chromium.org/2620463002/ )

Reason for revert:
Caused layout test failures.


http://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=...

Original issue's description:
> Show service worker navigation preload requests in DevTools Network tab.
> 
> Demo: https://youtu.be/I-Qe_Y-xYxE
> 
> Navigation Preload requests are initiated from the browser process.
> This is different from the normal network requests which are initiated from
the
> renderer process.
> 
> When the DevTools show the normal requests in the Network tab, DevTool's
> Network events (requestWillBeSent, responseReceived, loadingFinished etc) are
> dispatched via InspectorInstrumentation and InspectorNetworkAgent.
> 
> This CL introduces new DevTool's Network events (navigationPreloadSent,
> navigationPreloadResponseReceived, navigationPreloadFailed,
> navigationPreloadFinished) which are dispatched via InspectorInstrumentation
and
> InspectorNetworkAgent from ServiceWorkerContextClient.
> 
> In the normal requests case, we record the request sending timestamp when the
> renderer process will send the request in InspectorNetworkAgent::
> willSendRequestInternal(). But in the navigation preload case, we record the
> timestamp in the browser process, and send it to the service worker's renderer
> process using FetchEventPreloadHandle.
> 
> 
> BUG=649558
> 
> Review-Url: https://codereview.chromium.org/2620463002
> Cr-Commit-Position: refs/heads/master@{#445630}
> Committed:
https://chromium.googlesource.com/chromium/src/+/4c6b3b0f11b62e069d9d84ba99db...

TBR=falken@chromium.org,pfeldman@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=649558

Review-Url: https://codereview.chromium.org/2649923007
Cr-Commit-Position: refs/heads/master@{#445684}
Committed:
https://chromium.googlesource.com/chromium/src/+/f0d113c2a563169ac97086771a3e...
==========

[commit-bot: I haz the power, 2017-01-24 08:49:01]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/f0d113c2a563169ac97086771a3e...