BackgroundFetchRegistration.abort() should return a Promise.

BackgroundFetchRegistration.abort() should return a Promise.

This aligns our implementation with the following change that was pushed
to the specification last week:

  https://github.com/WICG/background-fetch/commit/cad906d
  "abort() now returns a promise for a boolean"

In addition, it also sets default values on the BackgroundFetchOptions
dictionary which is required to support the fact that it's optional in
the call to BackgroundFetchManager.fetch().

BUG=692534
Review-Url: https://codereview.chromium.org/2762663002
Cr-Commit-Position: refs/heads/master@{#458125}
Committed: https://chromium.googlesource.com/chromium/src/+/da265efafd1b4eca88d17ebd5ec032053fd733bb

[Peter Beverloo, 2017-03-20 14:59:21]

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

[Peter Beverloo, 2017-03-20 14:59:22]

+harkness for background fetch
+tsepez for Mojo callback

A test has been included, including a change detector ASSERT to make sure it's
updated when the BackgroundFetchServiceImpl starts doing something. (On which
I'll definitely CC you, Tom.)

[Peter Beverloo, 2017-03-20 15:03:55]

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

[commit-bot: I haz the power, 2017-03-20 15:04:18]

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

[harkness, 2017-03-20 16:57:09]

lgtm

[commit-bot: I haz the power, 2017-03-20 17:19:53]

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

[commit-bot: I haz the power, 2017-03-20 17:19:54]

Dry run: This issue passed the CQ dry run.

[Tom Sepez, 2017-03-20 17:23:34]

LGTM mojom

[Peter Beverloo, 2017-03-20 18:05:23]

The CQ bit was checked by peter@chromium.org

[commit-bot: I haz the power, 2017-03-20 18:06:19]

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-03-20 18:17:48]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1490033123051660, "parent_rev":
"6430db2fde6019843ea53e3540757857934b804a", "commit_rev":
"da265efafd1b4eca88d17ebd5ec032053fd733bb"}

[commit-bot: I haz the power, 2017-03-20 18:18:30]

Description was changed from

==========
BackgroundFetchRegistration.abort() should return a Promise.

This aligns our implementation with the following change that was pushed
to the specification last week:

  https://github.com/WICG/background-fetch/commit/cad906d
  "abort() now returns a promise for a boolean"

In addition, it also sets default values on the BackgroundFetchOptions
dictionary which is required to support the fact that it's optional in
the call to BackgroundFetchManager.fetch().

BUG=692534
==========

to

==========
BackgroundFetchRegistration.abort() should return a Promise.

This aligns our implementation with the following change that was pushed
to the specification last week:

  https://github.com/WICG/background-fetch/commit/cad906d
  "abort() now returns a promise for a boolean"

In addition, it also sets default values on the BackgroundFetchOptions
dictionary which is required to support the fact that it's optional in
the call to BackgroundFetchManager.fetch().

BUG=692534

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

[commit-bot: I haz the power, 2017-03-20 18:18:32]

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