| commit | ecd22f2fd5f2811b82ae7c540b8c1e40b9e9ce4f | [log] [tgz] |
|---|---|---|
| author | Colin Blundell <blundell@chromium.org> | Mon Nov 16 10:09:29 2020 |
| committer | Commit Bot <commit-bot@chromium.org> | Mon Nov 16 10:09:29 2020 |
| tree | aabcf8f7201008158f845b2a17a66cc46d38a55e | |
| parent | 32410c4f6c92a8019fabbf73520fcb91561771aa [diff] |
[WebLayer] Initial bringup of ad blocking This CL does the initial bringup of ad tagging and blocking functionality in WebLayer. To do so, we do the following: - Bring up an implementation of SubresourceFilterClient and attach it to WebContents instances - Instantiate subresource filter navigation throttles on navigation - Instantiates and configures SubresourceFilterAgent instances in the renderer The organization and code added is modeled after that in //chrome. We have left TODOs for significant pieces of functionality to be added in followups (e.g., showing of the infobar on Android). One thing to note is that ad tagging/blocking only triggers on Android in WebLayer, as it requires having a safe browsing database instance and WebLayer does not have one on platforms other than Android. This CL also adds browsertests of this initial functionality: - that the subresource filter activation state is computed on page loads - that ads are blocked on activated pages if they are flagged by the ruleset Bug: 1116095 Change-Id: I1db0136709014004c221bb0251551eaeac3538e3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2526087 Commit-Queue: Colin Blundell <blundell@chromium.org> Reviewed-by: Charlie Harrison <csharrison@chromium.org> Cr-Commit-Position: refs/heads/master@{#827735}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.