commit | 587b39ba215ae022e87b55b91fe273330e689cbe | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Mon Feb 03 08:19:53 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Feb 03 08:19:53 2025 |
tree | 0a6d9999174ca15ec96f3c6ba3d8af919e4ea461 | |
parent | 0cdc1fda5834112bee26e00847444a99055aa4df [diff] |
Roll DevTools Frontend from fb1c40ae65c3 to 7b31ea284807 (1 revision) https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/fb1c40ae65c3..7b31ea284807 2025-02-03 bmeurer@chromium.org [unified-css] Generate `sourceURL` annotation with relative path. 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:391381439 Change-Id: I249e5ba98309050072ea7caeeb2c9c239d08b155 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6222984 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@{#1414785}
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.