Use DeviceEventLogSource for Lacros Move DeviceEventLogSource from ash to common feedback folder. In the case of Lacros use it to write device_event_logs into feedback reports and into chrome://system report. This is an initial CL for creating a systemLog API for extensions that would support both Ash and Lacros. Bug: 1264234 Change-Id: I6e8269eb8d4493e806a9827aa0a2fafc5bb26c4e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4037661 Reviewed-by: Irem Uguz <iremuguz@google.com> Reviewed-by: Xiangdong Kong <xiangdongkong@google.com> Reviewed-by: Maria Petrisor <mpetrisor@chromium.org> Reviewed-by: Erik Chen <erikchen@chromium.org> Commit-Queue: Matej Aleksandrov <maleksandrov@chromium.org> Cr-Commit-Position: refs/heads/main@{#1074520}
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.