
Before this CL: Chrome would accept data objects that are either a string or a json object, and in both cases Chrome would pass them over to the platform and the wallet as a string in the request JSON After this CL: Chrome honors the format that the verifier used. If it's a string, it is forwarded as a string, otherwise as an JSON. This is to be aligned with the latest DC API spec. Bug: 357100947 Change-Id: If8ca07c6500bd6126281d8e999313ddbd2d6eb29 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6357471 Reviewed-by: Mike West <mkwst@chromium.org> Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org> Cr-Commit-Position: refs/heads/main@{#1437990}
Chromium
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.