[sync] Don't restrict to mainframe when exposing Javascript APIs There are plans to invoke the Javascript APIs from an iframe embedded in myaccount.google.com, to make sure that if the user changes their account password, the new account password is properly added as a recovery method, without counting on the less reliable server-side integration (reauth). Change-Id: I389d524a1800ec6ac13356a66268bc8a0781cb60 Bug: 1347763 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3779896 Reviewed-by: Alex Moshchuk <alexmos@chromium.org> Commit-Queue: Mikel Astiz <mastiz@chromium.org> Reviewed-by: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/main@{#1029119}
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.