summaryrefslogtreecommitdiffstats
path: root/chrome/renderer/content_settings_observer.h
Commit message (Expand)AuthorAgeFilesLines
* Remove static ContentSettingsObserver::default_settings_.marja@chromium.org2011-11-021-5/+6
* Delegating the "are images allowed" decision to renderer.marja@chromium.org2011-10-271-5/+16
* Check for default content setting pattern when requiring user authorization f...bauerb@chromium.org2011-10-191-0/+4
* Make RenderView inherit from content::RenderView, and add missing functions t...jam@chromium.org2011-10-101-1/+1
* Move RenderViewObserver and RenderViewObserverTracker to content\public\rende...jam@chromium.org2011-10-031-4/+4
* Revert 101944 - Experiment: Add a sync IPC call for every image load.marja@chromium.org2011-09-201-10/+0
* Experiment: Add a sync IPC call for every image load.marja@chromium.org2011-09-201-0/+10
* Update WebPermissionClient implementation to support image URLsjochen@chromium.org2011-09-191-1/+4
* Correctly apply content settings to data URLs.abarth@chromium.org2011-06-171-0/+7
* Cached response ContentSettingsObserver::AllowStoragejochen@chromium.org2011-06-011-0/+4
* Explicitly allow plug-ins once we received a message to load all blocked plug...bauerb@chromium.org2011-05-191-0/+3
* Chrome side of having the WebKit FileSystem API use WebPermissionClient for c...jam@chromium.org2011-05-121-0/+1
* More work on removing content settings code from src\content.jam@chromium.org2011-05-071-0/+7
* Chrome side to allow WebKit layer to use WebPermissionClient to check if acce...jam@chromium.org2011-05-041-0/+1
* Implement the new WebPermissionClient interface in Chrome code to get rid of ...jam@chromium.org2011-04-301-5/+11
* Move the content settings code out of RenderView, since it belongs in the Chr...jam@chromium.org2011-04-181-0/+74