commit | 1c34619967f42cbc23d07c541ca89bce56835a8d | [log] [tgz] |
---|---|---|
author | Fabio Rocha <fabio.rocha@microsoft.com> | Fri Feb 12 05:07:16 2021 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Feb 12 05:07:16 2021 |
tree | 9bc607e5a8d3f36d5b86d8ff6fe159499c3de421 | |
parent | 87c2acb754b2557736af7ea9c47b11b50cea7f86 [diff] |
Reland "desktop-pwas: Add web app protocol handler OS registration API" This is a reland of https://chromium-review.googlesource.com/c/chromium/src/+/2641333 - Reason for revert: it looks like this change was a suspect for a registerProtocolHandler test for extensions failing on mac. I'm thinking this was a false positive, as most changes in this CL should be no-ops. - Original change's description: desktop-pwas: Add web app protocol handler OS registration API Following the pattern of file_handlers, this CL introduces a simple protocol handler registration API that will have OS-specific files / implementations, starting with Windows. This API: 1. Consumes the web_app_handler_registration API to register the web app as an OS handler 2. Registers the protocol handler with ProtocolHandlerRegistry - left as a TODO to keep the CL small. No product behavior is expected with this CL since the API is not consumed yet. Bug: 1019239 Change-Id: I3fe0650ddc5f64e488c3a95f6dc0bfbf75e58e28 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2686758 Reviewed-by: Daniel Murphy <dmurph@chromium.org> Reviewed-by: Dominick Ng <dominickn@chromium.org> Commit-Queue: Fabio Rocha <fabio.rocha@microsoft.com> Cr-Commit-Position: refs/heads/master@{#853401}
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.