commit | 40be5ebccd845eabf6172fafc56b0a04584a3b1b | [log] [tgz] |
---|---|---|
author | Jacob Stanley <jacobstanley@google.com> | Wed Mar 19 17:06:55 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 19 17:06:55 2025 |
tree | 8afa578861cf42fd5a51749894ea9a72f53fbe17 | |
parent | 5240085bb2e55a7f81271a829cb470cc1ed53515 [diff] |
Updating out of date documentation in WebUI Explainer In the instructions of how the browser (c++) and Renderer (JS) communicate, there is a step to register the mojo PageHandlerFactory to your own controller. That step explained to do that in chrome/browser/chrome/browser_interface_binders.cc, however all of the registrations now exist in chrome/browser/chrome_browser_interface_binders_webui.cc This CL updates the doc with the correct path to register the Mojo PageHandlerFactory to your own controller. Change-Id: Ibdbb3041961a555fac044c6090f965850ade2b4e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6371454 Reviewed-by: Elly FJ <ellyjones@chromium.org> Commit-Queue: Jacob Stanley <jacobstanley@google.com> Auto-Submit: Jacob Stanley <jacobstanley@google.com> Cr-Commit-Position: refs/heads/main@{#1434902}
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.