[Subresource Filter] Add content settings-based adjustment to WebLayer
This CL incorporates Chrome's adjustment of subresource filter page activation decisions based on content settings within WebLayer. To do so, we have the shared SubresourceFilterSafeBrowsingActivationThrottle directly invoke the logic in question rather than having ChromeSubresourceFilterClient do so. That change necessitates some others, also made in this CL: - WebLayer brings up ProfileInteractionManager. - SubresourceFilterClient provides an accessor for ProfileInteractionManager. - SubresourceFilterSafeBrowsingActivationThrottle calls the adjustment logic via a new Delegate interface rather than doing so via SubresourceFilterClient. This interface is implemented by ProfileInteractionManager in production while allowing for porting of tests that provide custom (or nil) stub logic. We also add browsertests of this interaction in //weblayer. Note that this CL does not do any incorporation of the relevant *UI* for content/site settings of ad blocking in WebLayer; that will be followup work. This CL is a reland. The original CL was reverted due to the introduced tests failing on Win7. On inspection this turns out to be the issue tracked in crbug.com/1152429. I'm continuing to investigate that issue, but it's slow going so far. In the meantime this CL disables the newly-added tests on Windows with a reference to that bug (see diff between PS1, which is the original CL, and PS2). Bug: 1116095 Change-Id: I8dc8f3a2e08a58e91050cf9b484685ee4982f16f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627166Reviewed-by:Charlie Harrison <csharrison@chromium.org> Commit-Queue: Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/master@{#843619}
Showing
Please register or sign in to comment