commit | ff1d788c4e02846fb7c10e5857f686e28559c6cd | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Wed Jan 15 09:29:30 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jan 15 09:29:30 2025 |
tree | 9b11ff02ec6fdd70ba591f10529ce8cccbcb1ce5 | |
parent | 8fe8c7766d9b47bd043d4aae6339878d6de242b0 [diff] |
Roll DevTools Frontend from eb238929f5ce to 604b87a250dc (1 revision) https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/eb238929f5ce..604b87a250dc 2025-01-15 bmeurer@chromium.org [panels] Fix toolbar in Developer resources panel. 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: None Change-Id: Icda2511f40494129ab7d7c27d0422364dfd744e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6174611 Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1406586}
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.