diff options
| author | mihaip@chromium.org <mihaip@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-11-18 00:32:53 +0000 |
|---|---|---|
| committer | mihaip@chromium.org <mihaip@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-11-18 00:32:53 +0000 |
| commit | 8f0633691cd10779408642e2ad5eaa9b0c190b0a (patch) | |
| tree | 24395b8196731886a6e46b87b779d4cf09aba3d9 /content/browser/browsing_instance.h | |
| parent | ff3e5c4b85e2d4d93410841a4ca31a1707e7dac3 (diff) | |
| download | chromium_src-8f0633691cd10779408642e2ad5eaa9b0c190b0a.zip chromium_src-8f0633691cd10779408642e2ad5eaa9b0c190b0a.tar.gz chromium_src-8f0633691cd10779408642e2ad5eaa9b0c190b0a.tar.bz2 | |
When allowing an extension file:/// URL access, grant its process access to that scheme.
This allows XHRs from the background page to file:/// URLs to succeed. XHRs from
content scripts still fail, since they're running in a regular renderer process,
and there is currently no mechanism for only whitelisting the isolated world
within it for the file: scheme.
Also re-enable ExtensionApiTest.CrossOriginXHRContentScript since it doesn't
appear to have flaked recently.
BUG=104547,96725
R=aa@chromium.org
Review URL: http://codereview.chromium.org/8587052
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110614 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/browser/browsing_instance.h')
0 files changed, 0 insertions, 0 deletions