Exclude <webview> process from locking to chrome-guest:// site.
We need to fix this properly later on, but this should be fine for now.
Before the change, the issue here is:
<webview> loads http://www.google.com/
The SiteInstance of the <webview> looks like:
chrome-guest://appid, so it locks the guest process to that
site url.
When <webview> wants to read cookies from http://www.google.com,
ChildProcessSecurityPolicyImpl::SecurityState::CanAccessCookiesForOrigin()
return false and we kill the <webview> process b/c we think it's not
allowed to access the cookie.
This CL removes the origin lock for guest processes.
BUG=330264
Test=There's no way to check this @tott, patch in http://crrev.com/972313002,
Load a <webview> that accesses cookies, e.g. load http://www.google.com.
This should not result in killing renderer process anymore.
Review URL: https://codereview.chromium.org/1205983002
Cr-Commit-Position: refs/heads/master@{#336009}
1 file changed
