GitLab

Adds a browser-side security check that the frame making a
performance.measureMemory request is allowed to use the API, to guard
against compromised renderers skipping the renderer-side security check.
Currently it only checks that the frame is same-origin with the page's
main frame. Once an accessor for crossOriginIsolated status is added on
the browser side, the class can check that too.

R=fdoray

Bug: 1085129
Change-Id: I73b1955dafa0dec248e86783aee4e8d8e4cdcda1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2588249Reviewed-by: François Doray <fdoray@chromium.org>
Commit-Queue: Joe Mason <joenotcharles@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837160}