commit | 237d77ca68ed05deeb4b9cfadc1229f079a2c505 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Tue Feb 18 12:59:25 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Feb 18 12:59:25 2025 |
tree | 12567875abfbae745423428d8645de0a7fc1a48f | |
parent | 8a9c26e14c48148467e2efeb57eaf37d317a3c80 [diff] |
Roll DevTools Frontend from b36a46bc5462 to f4ee86a6a319 (3 revisions) https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/b36a46bc5462..f4ee86a6a319 2025-02-18 changhaohan@chromium.org Add interest target linking 2025-02-18 jacktfranklin@chromium.org AI: Format and sanitize trace network requests 2025-02-18 nvitkov@chromium.org [eslint] Add rule `only-throw-error` 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:393244954,chromium:394552594,chromium:397260638 Change-Id: I148ae429073602659838ce39da8fe5b4c983d2dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6278409 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@{#1421329}
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.