Correctly apply content settings to data URLs.

Data URLs don't round-trip through the browser's network stack, so they don't
trigger the content settings code to upload the proper settings to the
renderer.  This patch proactively pushes the default content settings into the
renderer so that it can use them for data URLs (and other sandboxed frames).

Review URL: http://codereview.chromium.org/7167003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@89466 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 1 insertions, 0 deletions

diff --git a/chrome/renderer/chrome_render_process_observer.h b/chrome/renderer/chrome_render_process_observer.h
index f447c82..beb2b26 100644
--- a/chrome/renderer/chrome_render_process_observer.h
+++ b/chrome/renderer/chrome_render_process_observer.h
@@ -35,6 +35,7 @@ class ChromeRenderProcessObserver : public RenderProcessObserver {
   void OnSetIsIncognitoProcess(bool is_incognito_process);
   void OnSetContentSettingsForCurrentURL(
       const GURL& url, const ContentSettings& content_settings);
+  void OnSetDefaultContentSettings(const ContentSettings& content_settings);
   void OnSetCacheCapacities(size_t min_dead_capacity,
                             size_t max_dead_capacity,
                             size_t capacity);