-
msw authored
Revert of Enforce capability spec renderer <--> browser (patchset #14 id:260001 of https://codereview.chromium.org/2259903002/ ) Reason for revert: Numerous failures; some examples: https://build.chromium.org/p/chromium.win/builders/Win7%20%2832%29%20Tests/builds/10021 https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Win7/builds/45903 https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Mac10.9/builds/36939 https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Linux/builds/70401 Potentially related: https://build.chromium.org/p/chromium.mac/builders/Mac10.9%20Tests/builds/28370 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 > Cr-Original-Original-Commit-Position: refs/heads/master@{#418282} > Cr-Original-Commit-Position: refs/heads/master@{#418398} > Cr-Commit-Position: refs/heads/master@{#418582} 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 Review-Url: https://codereview.chromium.org/2342523003 Cr-Commit-Position: refs/heads/master@{#418614}
be633a43
