Fix origin lock state on chrome://process-internals.
chrome://process-internals calculates and displays each process's locked state by checking lock_url(). That won't give the correct result, since lock_url() is computed before we lock the process, and having it doesn't imply that the process will actually be locked in the future. Fix this to check the process's lock in ChildProcessSecurityPolicy, which should always given the correct result. Bug: 850087 Change-Id: Ibf5e37fc69919e6c1e6a7e67943942cf6c93242d Reviewed-on: https://chromium-review.googlesource.com/c/1287953Reviewed-by:Nasko Oskov <nasko@chromium.org> Commit-Queue: Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#601655}
Showing
Please register or sign in to comment