Fire the `backgroundfetchabort` event for aborted fetches

Fire the `backgroundfetchabort` event for aborted fetches

When the status of a completed fetch is ABORTED, which can be caused by
either the user (by using the notification) or the developer (by calling
abort() on the registration), fire the aforementioned event.

BUG=706831
Review-Url: https://codereview.chromium.org/2824223002
Cr-Commit-Position: refs/heads/master@{#465263}
Committed: https://chromium.googlesource.com/chromium/src/+/438975fc49827c2b419b0c173570c4604c74c59b

[Peter Beverloo, 2017-04-18 14:28:09]

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

[Peter Beverloo, 2017-04-18 14:28:14]

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

[Peter Beverloo, 2017-04-18 14:28:15]

+harkness for review

[commit-bot: I haz the power, 2017-04-18 14:28:25]

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 15:40:41]

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

[commit-bot: I haz the power, 2017-04-18 15:40:42]

Dry run: This issue passed the CQ dry run.

[harkness, 2017-04-18 16:03:46]

lgtm

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

The CQ bit was checked by peter@chromium.org

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

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:39:17]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1492532814201840, "parent_rev":
"929fcfc0778b8848e9a4b2b5c205c1ae43cfa9f9", "commit_rev":
"438975fc49827c2b419b0c173570c4604c74c59b"}

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

Description was changed from

==========
Fire the `backgroundfetchabort` event for aborted fetches

When the status of a completed fetch is ABORTED, which can be caused by
either the user (by using the notification) or the developer (by calling
abort() on the registration), fire the aforementioned event.

BUG=706831
==========

to

==========
Fire the `backgroundfetchabort` event for aborted fetches

When the status of a completed fetch is ABORTED, which can be caused by
either the user (by using the notification) or the developer (by calling
abort() on the registration), fire the aforementioned event.

BUG=706831

Review-Url: https://codereview.chromium.org/2824223002
Cr-Commit-Position: refs/heads/master@{#465263}
Committed:
https://chromium.googlesource.com/chromium/src/+/438975fc49827c2b419b0c173570...
==========

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

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