commit | 1f27eb136606ab67fdd45f6e912e093792263f10 | [log] [tgz] |
---|---|---|
author | Yuki Shiino <yukishiino@chromium.org> | Thu Jul 29 05:31:39 2021 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jul 29 05:31:39 2021 |
tree | 38fb3c8ac1ba28e738a2937ca54acb291cb4c8b6 | |
parent | 76145dd56fbbe43398d32764ba226d23e6021717 [diff] |
Revert "[Files SWA]: Chrome App API cleanup" This reverts commit 0a1158be66a6730d0d8a3d7c9295783cd39fc7e2. Reason for revert: Suspicious about test failures of FilesAppBrowserTest.Test https://ci.chromium.org/ui/p/chromium/builders/ci/Linux%20ChromiumOS%20MSan%20Tests/24408/test-results Original change's description: > [Files SWA]: Chrome App API cleanup > > Removing dependencies on chrome.runtime.getManifest and > chrome.runtime.getURL APIs. Since those require URLs based > on the Files App ID (host), adds url_constants.js. > The new module centralizes building File Manager URLs for > files. > > Bug: b/194251406, b/194251405 > Change-Id: Ifae98ead43db329c45afac054df9f72709d58cdf > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3056256 > Reviewed-by: Luciano Pacheco <lucmult@chromium.org> > Commit-Queue: Bo Majewski <majewski@chromium.org> > Cr-Commit-Position: refs/heads/master@{#906435} Bug: b/194251406, b/194251405 Change-Id: I9ba98f5c8bfc706eab0d2ad752ba86b86860058d No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3058165 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Owners-Override: Yuki Shiino <yukishiino@chromium.org> Cr-Commit-Position: refs/heads/master@{#906585}
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.