Revert of Enforce capability spec renderer <--> browser

Revert of Enforce capability spec renderer <--> browser (patchset #19 id:360001 of https://codereview.chromium.org/2259903002/ )

Reason for revert:
Speculative revert to fix breakage here:

https://build.chromium.org/p/chromium.memory.full/builders/Linux%20TSan%20Tests/builds/1670

Original issue's description:
> Enforce capability spec renderer <--> browser.
>
> This implements:
>
> - allows the content embedder to merge a manifest into the base ones provided by content, allowing it to add to the list of interfaces exposed to the renderer.
> - adds such an overlay to chrome/browser
>
> So.. from now on if you add an interface to either the browser/renderer, you'll need to list it in the manifest. I wonder how we should broadcast this. Also as a separate step we should require these manifests get security review.
>
> R=rockot@chromium.org,tsepez@chromium.org
>
> Committed: https://crrev.com/4ea17059bf78553528f3ffb4a9de84a447622fd3
> Committed: https://crrev.com/807a926c9ca02ac8ae1b52e82537834ef78fb9ba
> Committed: https://crrev.com/91c25a3cedc4fadcb8c84e91cc59a8f90411058a
> Committed: https://crrev.com/cdf40b4b434b43af6accf0c822ea964bc6bfd931
> Committed: https://crrev.com/8b277b0bd73aa544f0d5e38a8763658d3e807880
> Cr-Original-Original-Original-Original-Commit-Position: refs/heads/master@{#418282}
> Cr-Original-Original-Original-Commit-Position: refs/heads/master@{#418398}
> Cr-Original-Original-Commit-Position: refs/heads/master@{#418582}
> Cr-Original-Commit-Position: refs/heads/master@{#418691}
> Cr-Commit-Position: refs/heads/master@{#418988}

TBR=rockot@chromium.org,tsepez@chromium.org,ben@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true

Committed: https://crrev.com/5a97afd17b75389af80e732d7722760c0f41744d
Cr-Commit-Position: refs/heads/master@{#419188}

[tommycli, 2016-09-16 16:40:40]

The CQ bit was checked by tommycli@chromium.org

[tommycli, 2016-09-16 16:40:40]

Created Revert of Enforce capability spec renderer <--> browser

[commit-bot: I haz the power, 2016-09-16 16:41:07]

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-09-16 16:42:38]

Description was changed from

==========
Revert of Enforce capability spec renderer <--> browser (patchset #19 id:360001
of https://codereview.chromium.org/2259903002/ )

Reason for revert:
Speculative revert to fix breakage here:

https://build.chromium.org/p/chromium.memory.full/builders/Linux%20TSan%20Tes...

Original issue's description:
> Enforce capability spec renderer <--> browser.
> 
> This implements:
> 
> - allows the content embedder to merge a manifest into the base ones provided
by content, allowing it to add to the list of interfaces exposed to the
renderer.
> - adds such an overlay to chrome/browser
> 
> So.. from now on if you add an interface to either the browser/renderer,
you'll need to list it in the manifest. I wonder how we should broadcast this.
Also as a separate step we should require these manifests get security review.
> 
> R=rockot@chromium.org,tsepez@chromium.org
> 
> Committed: https://crrev.com/4ea17059bf78553528f3ffb4a9de84a447622fd3
> Committed: https://crrev.com/807a926c9ca02ac8ae1b52e82537834ef78fb9ba
> Committed: https://crrev.com/91c25a3cedc4fadcb8c84e91cc59a8f90411058a
> Committed: https://crrev.com/cdf40b4b434b43af6accf0c822ea964bc6bfd931
> Committed: https://crrev.com/8b277b0bd73aa544f0d5e38a8763658d3e807880
> Cr-Original-Original-Original-Original-Commit-Position:
refs/heads/master@{#418282}
> Cr-Original-Original-Original-Commit-Position: refs/heads/master@{#418398}
> Cr-Original-Original-Commit-Position: refs/heads/master@{#418582}
> Cr-Original-Commit-Position: refs/heads/master@{#418691}
> Cr-Commit-Position: refs/heads/master@{#418988}

TBR=rockot@chromium.org,tsepez@chromium.org,ben@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
==========

to

==========
Revert of Enforce capability spec renderer <--> browser (patchset #19 id:360001
of https://codereview.chromium.org/2259903002/ )

Reason for revert:
Speculative revert to fix breakage here:

https://build.chromium.org/p/chromium.memory.full/builders/Linux%20TSan%20Tes...

Original issue's description:
> Enforce capability spec renderer <--> browser.
> 
> This implements:
> 
> - allows the content embedder to merge a manifest into the base ones provided
by content, allowing it to add to the list of interfaces exposed to the
renderer.
> - adds such an overlay to chrome/browser
> 
> So.. from now on if you add an interface to either the browser/renderer,
you'll need to list it in the manifest. I wonder how we should broadcast this.
Also as a separate step we should require these manifests get security review.
> 
> R=rockot@chromium.org,tsepez@chromium.org
> 
> Committed: https://crrev.com/4ea17059bf78553528f3ffb4a9de84a447622fd3
> Committed: https://crrev.com/807a926c9ca02ac8ae1b52e82537834ef78fb9ba
> Committed: https://crrev.com/91c25a3cedc4fadcb8c84e91cc59a8f90411058a
> Committed: https://crrev.com/cdf40b4b434b43af6accf0c822ea964bc6bfd931
> Committed: https://crrev.com/8b277b0bd73aa544f0d5e38a8763658d3e807880
> Cr-Original-Original-Original-Original-Commit-Position:
refs/heads/master@{#418282}
> Cr-Original-Original-Original-Commit-Position: refs/heads/master@{#418398}
> Cr-Original-Original-Commit-Position: refs/heads/master@{#418582}
> Cr-Original-Commit-Position: refs/heads/master@{#418691}
> Cr-Commit-Position: refs/heads/master@{#418988}

TBR=rockot@chromium.org,tsepez@chromium.org,ben@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
==========

[commit-bot: I haz the power, 2016-09-16 16:42:40]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-09-16 16:45:15]

Description was changed from

==========
Revert of Enforce capability spec renderer <--> browser (patchset #19 id:360001
of https://codereview.chromium.org/2259903002/ )

Reason for revert:
Speculative revert to fix breakage here:

https://build.chromium.org/p/chromium.memory.full/builders/Linux%20TSan%20Tes...

Original issue's description:
> Enforce capability spec renderer <--> browser.
> 
> This implements:
> 
> - allows the content embedder to merge a manifest into the base ones provided
by content, allowing it to add to the list of interfaces exposed to the
renderer.
> - adds such an overlay to chrome/browser
> 
> So.. from now on if you add an interface to either the browser/renderer,
you'll need to list it in the manifest. I wonder how we should broadcast this.
Also as a separate step we should require these manifests get security review.
> 
> R=rockot@chromium.org,tsepez@chromium.org
> 
> Committed: https://crrev.com/4ea17059bf78553528f3ffb4a9de84a447622fd3
> Committed: https://crrev.com/807a926c9ca02ac8ae1b52e82537834ef78fb9ba
> Committed: https://crrev.com/91c25a3cedc4fadcb8c84e91cc59a8f90411058a
> Committed: https://crrev.com/cdf40b4b434b43af6accf0c822ea964bc6bfd931
> Committed: https://crrev.com/8b277b0bd73aa544f0d5e38a8763658d3e807880
> Cr-Original-Original-Original-Original-Commit-Position:
refs/heads/master@{#418282}
> Cr-Original-Original-Original-Commit-Position: refs/heads/master@{#418398}
> Cr-Original-Original-Commit-Position: refs/heads/master@{#418582}
> Cr-Original-Commit-Position: refs/heads/master@{#418691}
> Cr-Commit-Position: refs/heads/master@{#418988}

TBR=rockot@chromium.org,tsepez@chromium.org,ben@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
==========

to

==========
Revert of Enforce capability spec renderer <--> browser (patchset #19 id:360001
of https://codereview.chromium.org/2259903002/ )

Reason for revert:
Speculative revert to fix breakage here:

https://build.chromium.org/p/chromium.memory.full/builders/Linux%20TSan%20Tes...

Original issue's description:
> Enforce capability spec renderer <--> browser.
>
> This implements:
>
> - allows the content embedder to merge a manifest into the base ones provided
by content, allowing it to add to the list of interfaces exposed to the
renderer.
> - adds such an overlay to chrome/browser
>
> So.. from now on if you add an interface to either the browser/renderer,
you'll need to list it in the manifest. I wonder how we should broadcast this.
Also as a separate step we should require these manifests get security review.
>
> R=rockot@chromium.org,tsepez@chromium.org
>
> Committed: https://crrev.com/4ea17059bf78553528f3ffb4a9de84a447622fd3
> Committed: https://crrev.com/807a926c9ca02ac8ae1b52e82537834ef78fb9ba
> Committed: https://crrev.com/91c25a3cedc4fadcb8c84e91cc59a8f90411058a
> Committed: https://crrev.com/cdf40b4b434b43af6accf0c822ea964bc6bfd931
> Committed: https://crrev.com/8b277b0bd73aa544f0d5e38a8763658d3e807880
> Cr-Original-Original-Original-Original-Commit-Position:
refs/heads/master@{#418282}
> Cr-Original-Original-Original-Commit-Position: refs/heads/master@{#418398}
> Cr-Original-Original-Commit-Position: refs/heads/master@{#418582}
> Cr-Original-Commit-Position: refs/heads/master@{#418691}
> Cr-Commit-Position: refs/heads/master@{#418988}

TBR=rockot@chromium.org,tsepez@chromium.org,ben@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true

Committed: https://crrev.com/5a97afd17b75389af80e732d7722760c0f41744d
Cr-Commit-Position: refs/heads/master@{#419188}
==========

[commit-bot: I haz the power, 2016-09-16 16:45:17]

Patchset 1 (id:??) landed as
https://crrev.com/5a97afd17b75389af80e732d7722760c0f41744d
Cr-Commit-Position: refs/heads/master@{#419188}