| commit | 576c5f5380b51d869a95c38718d958a6dac7d72c | [log] [tgz] |
|---|---|---|
| author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Fri Feb 07 11:18:04 2025 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Feb 07 11:18:04 2025 |
| tree | 7b061d0dd7aedb8827d0538b809c26f7cb0ed177 | |
| parent | 292014da327c8bf98ad2e916cc0bc7cb65310d10 [diff] |
Roll DevTools Frontend from 59a7edb40b42 to de5d1aaf36e2 (2 revisions) https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/59a7edb40b42..de5d1aaf36e2 2025-02-07 andoli@chromium.org Remove manual support of JS scheduling events 2025-02-07 paulirish@chromium.org RPP: Add VE for long-critical-network-tree 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:372897712 Change-Id: I2375fddbe5c08099ae0fb480ebf92d3e1e909dd4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6242887 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@{#1417242}
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.