Fire the `backgroundfetchfail` event for failed fetches

Fire the `backgroundfetchfail` event for failed fetches

Background Fetches that contain a failed request (e.g. 404) will now
cause the `backgroundfetchfail` event to be fired as opposed to the
`backgroundfetched` event. For now, inaccessible CORS requests will be
considered as failures as well.

BUG=692579
Review-Url: https://codereview.chromium.org/2816403004
Cr-Commit-Position: refs/heads/master@{#465262}
Committed: https://chromium.googlesource.com/chromium/src/+/929fcfc0778b8848e9a4b2b5c205c1ae43cfa9f9

[Peter Beverloo, 2017-04-18 14:06:22]

The CQ bit was checked by peter@chromium.org to run a CQ dry run

[Peter Beverloo, 2017-04-18 14:06:30]

peter@chromium.org changed reviewers:
+ harkness@chromium.org

[Peter Beverloo, 2017-04-18 14:06:31]

+harkness

[commit-bot: I haz the power, 2017-04-18 14:06:39]

Dry run: 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-04-18 14:57:37]

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

[commit-bot: I haz the power, 2017-04-18 14:57:38]

Dry run: This issue passed the CQ dry run.

[harkness, 2017-04-18 16:06:42]

lgtm

[Peter Beverloo, 2017-04-18 16:26:52]

The CQ bit was checked by peter@chromium.org

[commit-bot: I haz the power, 2017-04-18 16:27:27]

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-04-18 16:31:02]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1492532812153420, "parent_rev":
"0c3cb9bf34a6462f2d9dca31b71cac01f9853104", "commit_rev":
"929fcfc0778b8848e9a4b2b5c205c1ae43cfa9f9"}

[commit-bot: I haz the power, 2017-04-18 16:31:10]

Description was changed from

==========
Fire the `backgroundfetchfail` event for failed fetches

Background Fetches that contain a failed request (e.g. 404) will now
cause the `backgroundfetchfail` event to be fired as opposed to the
`backgroundfetched` event. For now, inaccessible CORS requests will be
considered as failures as well.

BUG=692579
==========

to

==========
Fire the `backgroundfetchfail` event for failed fetches

Background Fetches that contain a failed request (e.g. 404) will now
cause the `backgroundfetchfail` event to be fired as opposed to the
`backgroundfetched` event. For now, inaccessible CORS requests will be
considered as failures as well.

BUG=692579

Review-Url: https://codereview.chromium.org/2816403004
Cr-Commit-Position: refs/heads/master@{#465262}
Committed:
https://chromium.googlesource.com/chromium/src/+/929fcfc0778b8848e9a4b2b5c205...
==========

[commit-bot: I haz the power, 2017-04-18 16:31:12]

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