commit | 004786a4bca997d71618c8fc0b3f0c98ea660c27 | [log] [tgz] |
---|---|---|
author | msiem <msiem@chromium.org> | Tue Feb 25 02:34:53 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Feb 25 02:34:53 2025 |
tree | 791f2e90b950c4c407bdff15d75101bb2b3d920c | |
parent | fe19fbb00c6020edde8b8f3deb99e9377af7b7b8 [diff] |
Map WebDXFeature use counters for Fugu This CL maps existing counters that are representative of the feature usage: - app-file-handlers: WebDXFeatures::kAppFileHandlers is recorded when launch files are set in the web_launch_service_impl.cc - app-protocol-handlers: WebDXFeatures::kAppProtocolHandlers is recorded if the manifest's protocol handler is not empty. Found in the manifest_manager.cc - badging: WebDXFeatures::kBadging is recorded when installed web applications display an application badge. This feature is used in navigator_badge.cc when setAppBadge() is called. - manifest: WebDXFeatures::kManifest is recorded when any manifest metadata about a site is collected. Aside from the name, icon, and descriptions, this also includes ways in which the app wishes to integrate with the device. More info: https://github.com/web-platform-dx/web features/blob/main/features/manifest.yml - beforeInstallPrompt: WebDXFeatures::kBeforeInstallPrompt is recorded when an event prompt shows up and is completed for a site that is installable as a PWA. Change-Id: I069ac1eb8abc2b71ddb800c44b05cc56f218cdae Bug: 379953791 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6299834 Commit-Queue: May Siem <msiem@chromium.org> Reviewed-by: Dibyajyoti Pal <dibyapal@chromium.org> Cr-Commit-Position: refs/heads/main@{#1424277}
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.