commit | 3f5534cd70a8a3cdf534667b1e3f2c8ca5b6b9b7 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Mon Jul 28 13:21:50 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jul 28 13:21:50 2025 |
tree | 5ac353a08ede687c56647f2d9acc80aa1a13835d | |
parent | 19ff4aaa35264eb72e83ae2f733f85a65e2b618d [diff] |
Roll DevTools Frontend from f69a361b3207 to 70991917bd8d (2 revisions) https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/f69a361b3207..70991917bd8d 2025-07-28 dsv@chromium.org Re-baseline timeline screenshot test 2025-07-28 jacktfranklin@chromium.org RPP: add hover VE logs for flamecharts 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 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:432445929 Change-Id: I6eae8a52207e0ecb8fa319682e0774b9d2b56eb7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6792248 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@{#1492758}
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.