[Extensions Bindings] Apply per-context restrictions to events

[Extensions Bindings] Apply per-context restrictions to events

Similar to functions, API events can be restricted on a per-context
basis. Apply the same deletion logic to them if they are unavailable
in the given context.

Modify APIBinding unittests to reflect this, and add more comprehensive
tests in NativeExtensionBindingsSystem to test APIs that can be
partially-available to websites.

BUG=653596
Review-Url: https://codereview.chromium.org/2821793003
Cr-Commit-Position: refs/heads/master@{#465736}
Committed: https://chromium.googlesource.com/chromium/src/+/89c1673e0dd340f486eba92816998f839706d8f9

[Devlin, 2017-04-17 15:13:14]

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

[commit-bot: I haz the power, 2017-04-17 15:13:25]

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

[Devlin, 2017-04-17 15:19:39]

Description was changed from

==========
[Extensions Bindings] Apply per-context restrictions to events

Similar to functions, API events can be restricted on a per-context
basis. Apply the same deletion logic to them if they are unavailable
in the given context.

Modify APIBinding unittests to reflect this, and add more comprehensive
tests in NativeExtensionBindingsSystem to test APIs that can be
partially-available to websites.

BUG=
==========

to

==========
[Extensions Bindings] Apply per-context restrictions to events

Similar to functions, API events can be restricted on a per-context
basis. Apply the same deletion logic to them if they are unavailable
in the given context.

Modify APIBinding unittests to reflect this, and add more comprehensive
tests in NativeExtensionBindingsSystem to test APIs that can be
partially-available to websites.

BUG=653596
==========

[commit-bot: I haz the power, 2017-04-17 15:32:44]

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

[commit-bot: I haz the power, 2017-04-17 15:32:44]

Dry run: Try jobs failed on following builders:
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[Devlin, 2017-04-17 16:58:07]

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

[commit-bot: I haz the power, 2017-04-17 16:58: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-17 17:38:07]

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

[commit-bot: I haz the power, 2017-04-17 17:38:08]

Dry run: This issue passed the CQ dry run.

[Devlin, 2017-04-17 17:39:56]

rdevlin.cronin@chromium.org changed reviewers:
+ jbroman@chromium.org, lazyboy@chromium.org

[Devlin, 2017-04-17 17:39:56]

Hey folks, mind taking a look?

[jbroman, 2017-04-19 18:56:30]

lgtm

[lazyboy, 2017-04-19 19:37:28]

lgtm

[Devlin, 2017-04-19 19:39:26]

The CQ bit was checked by rdevlin.cronin@chromium.org

[commit-bot: I haz the power, 2017-04-19 19:39:53]

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-19 20:39:41]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1492630766414660,
"parent_rev": "438c2eb7315f961aff2a38c937c8f8c415c40924", "commit_rev":
"89c1673e0dd340f486eba92816998f839706d8f9"}

[commit-bot: I haz the power, 2017-04-19 20:40:00]

Description was changed from

==========
[Extensions Bindings] Apply per-context restrictions to events

Similar to functions, API events can be restricted on a per-context
basis. Apply the same deletion logic to them if they are unavailable
in the given context.

Modify APIBinding unittests to reflect this, and add more comprehensive
tests in NativeExtensionBindingsSystem to test APIs that can be
partially-available to websites.

BUG=653596
==========

to

==========
[Extensions Bindings] Apply per-context restrictions to events

Similar to functions, API events can be restricted on a per-context
basis. Apply the same deletion logic to them if they are unavailable
in the given context.

Modify APIBinding unittests to reflect this, and add more comprehensive
tests in NativeExtensionBindingsSystem to test APIs that can be
partially-available to websites.

BUG=653596

Review-Url: https://codereview.chromium.org/2821793003
Cr-Commit-Position: refs/heads/master@{#465736}
Committed:
https://chromium.googlesource.com/chromium/src/+/89c1673e0dd340f486eba9281699...
==========

[commit-bot: I haz the power, 2017-04-19 20:40:01]

Committed patchset #3 (id:40001) as
https://chromium.googlesource.com/chromium/src/+/89c1673e0dd340f486eba9281699...