Revert of Mojoify FetchEvent of Service Worker.

Revert of Mojoify FetchEvent of Service Worker. (patchset #8 id:330001 of https://codereview.chromium.org/2352173004/ )

Reason for revert:
Crashes in Canary: crbug.com/653403

Original issue's description:
> Mojoify FetchEvent of Service Worker.
> 
> I'd like to use Mojo to send navigation preload response (crbug.com/649558) from
> the browser process to the service worker. But currently we are using the legacy
> IPC when the browser process sends the FetchEvent to the service worker. There
> will be an ordering issue if we use both the legacy IPC and Mojo IPC.
> 
> To avoid the ordering issue, this CL changes the FetchEvent IPC to use Mojo.
> 
> BUG=629701, 649558
> 
> Committed: https://crrev.com/bdc8e1e4477f7dcd911528720a50d639be6d39b5
> Cr-Commit-Position: refs/heads/master@{#422996}

TBR=shimazu@chromium.org,dcheng@chromium.org,clamy@chromium.org,horo@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=629701, 649558

[garykac, 2016-10-06 18:28:48]

The CQ bit was checked by garykac@chromium.org

[garykac, 2016-10-06 18:28:48]

Created Revert of Mojoify FetchEvent of Service Worker.

[commit-bot: I haz the power, 2016-10-06 18:29:38]

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, 2016-10-06 18:33:27]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-06 18:33:29]

Try jobs failed on following builders:
  ios-device on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)
  ios-simulator on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/bui...)
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[dcheng, 2016-10-07 21:10:46]

Closing because this was already reverted in a separate CL.

[dcheng, 2016-10-07 21:10:58]

Description was changed from

==========
Revert of Mojoify FetchEvent of Service Worker. (patchset #8 id:330001 of
https://codereview.chromium.org/2352173004/ )

Reason for revert:
Crashes in Canary: crbug.com/653403

Original issue's description:
> Mojoify FetchEvent of Service Worker.
> 
> I'd like to use Mojo to send navigation preload response (crbug.com/649558)
from
> the browser process to the service worker. But currently we are using the
legacy
> IPC when the browser process sends the FetchEvent to the service worker. There
> will be an ordering issue if we use both the legacy IPC and Mojo IPC.
> 
> To avoid the ordering issue, this CL changes the FetchEvent IPC to use Mojo.
> 
> BUG=629701,649558
> 
> Committed: https://crrev.com/bdc8e1e4477f7dcd911528720a50d639be6d39b5
> Cr-Commit-Position: refs/heads/master@{#422996}

TBR=shimazu@chromium.org,dcheng@chromium.org,clamy@chromium.org,horo@chromium...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=629701,649558
==========

to

==========
Revert of Mojoify FetchEvent of Service Worker. (patchset #8 id:330001 of
https://codereview.chromium.org/2352173004/ )

Reason for revert:
Crashes in Canary: crbug.com/653403

Original issue's description:
> Mojoify FetchEvent of Service Worker.
> 
> I'd like to use Mojo to send navigation preload response (crbug.com/649558)
from
> the browser process to the service worker. But currently we are using the
legacy
> IPC when the browser process sends the FetchEvent to the service worker. There
> will be an ordering issue if we use both the legacy IPC and Mojo IPC.
> 
> To avoid the ordering issue, this CL changes the FetchEvent IPC to use Mojo.
> 
> BUG=629701,649558
> 
> Committed: https://crrev.com/bdc8e1e4477f7dcd911528720a50d639be6d39b5
> Cr-Commit-Position: refs/heads/master@{#422996}

TBR=shimazu@chromium.org,dcheng@chromium.org,clamy@chromium.org,horo@chromium...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=629701,649558
==========