commit | 761946c3175576b6e72c0d59ed19c6bd4e677812 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Fri Dec 13 02:27:53 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Dec 13 02:27:53 2024 |
tree | 5c5ce7152ed773440c74ff0cf8458664f36c56a9 | |
parent | 5c76698b42de4c782f994d0444b6095dc70396cc [diff] |
Roll DevTools Frontend from 629b0a193aff to 47bdf18dd943 (1 revision) https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/629b0a193aff..47bdf18dd943 2024-12-13 asraine@chromium.org [RPP] Add DOM size insight component to experimental insights If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@rotations.google.com,liviurau@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Bug: chromium:372897811 Change-Id: Idf4bf0405da44f2e009f8414157cb0a8dda374db Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6092720 Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1395731}
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.