| commit | d1c5fda3e4387672e25c656d6cc27c9d7ea7fe4a | [log] [tgz] |
|---|---|---|
| author | Daniel Murphy <dmurph@chromium.org> | Fri Aug 25 00:05:11 2023 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Aug 25 00:05:11 2023 |
| tree | be9d26e3a56d79e0fdd6c300520a476adbe6ac1a | |
| parent | a312bcd4e4af19bf2b15d643606f1875aa779bcd [diff] |
[apps] Pull out user link capturing throttle logic for cross-platform
This change refactors the user link capturing logic inside of both
the AppsNavigationThrottle and the ChromeOsAppsNavigationThrottle into
the LinkCapturingNavigationThrottle with a Delegate class for per-
platform specialization.
This split divorces the core link capturing logic from both
App Service and web apps systems so it can be bound to either as a
provider of apps with URL scopes.
The dependency graph will be:
ChromeContentBrowserClient
/ | \
v | v
WebAppLinkCapturing (next) | AppServiceLinkCapturing
\ | /
v v v
LinkCapturingNavigationThrottle
Design doc: go/user-link-capturing-throttle
The next patch will create the throttle used for non-CrOS platforms.
Bug: b/269773608
Change-Id: I693ab4b78bd4ed61ba4e641b5f167d64c5a4969c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4727423
Reviewed-by: Yuichiro Hanada <yhanada@chromium.org>
Reviewed-by: Yilkal Abe <yilkal@chromium.org>
Reviewed-by: Dibyajyoti Pal <dibyapal@chromium.org>
Reviewed-by: Alan Cutter <alancutter@chromium.org>
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Tim Sergeant <tsergeant@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1188097}
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.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
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.
If you found a bug, please file it at https://crbug.com/new.