[Subresource Filter] Prep ContentSettingsManager for history dep removal
WebLayer does not use //components/history and does not want to take a dep on the (large) component, as every dep that WebLayer adds has an impact on WebView. SubresourceFilterContentSettingsManager, however, currently depends on //components/history for its optional observance of the user's deletion of URLs from history. This CL prepares for abstraction of that dependency by having SubresourceFilterContentSettingsManager::OnURLsDeleted() operate on new public APIs of ContentSettingsManager for deleting site metadata. A followup CL will then do the following: - Add the ability for SubresourceFilterProfileContext to store opaque embedder data (via a simple SubresourceFilterProfileContext::EmbedderData interface) - Move the history observance to a new SubresourceFilterHistoryObserver class that is an EmbedderData and takes in a SubresourceFilterContentSettingsManager instance to call into - Have SubresourceFilterProfileContextFactory create SubresourceFilterHistoryObserver to be stored by SubresourceFilterProfileContext instances In this way, WebLayer will be able to use SubresourceFilterProfileContext, AdsInterventionManager, and SubresourceFilterContentSettingsManager without taking on the //components/history dep. Bug: 1116095 Change-Id: Icf20e19722ce4b728645b157d513194cbfefec6b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2464264Reviewed-by:Eric Robinson <ericrobinson@chromium.org> Commit-Queue: Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/master@{#816463}
Showing
Please register or sign in to comment