Roll DevTools Frontend from 6df8343a931d to 5cb2df83c69e (9 revisions)

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/6df8343a931d..5cb2df83c69e

2026-05-06 samiyac@google.com Migrate sources/debugger-breakpoints/dom-breakpoints-reload to e2e test
2026-05-06 alexrudenko@chromium.org Partially move core/sdk tests to node
2026-05-06 jacktfranklin@chromium.org AI: improve main thread lookup
2026-05-06 samiyac@google.com Simplify AI completion/generation feature availability checks
2026-05-06 liviurau@chromium.org Revert "AI: remove GCA migration from default feature flags"
2026-05-06 alexrudenko@chromium.org Migrate workspace model to foundation
2026-05-06 fmacintosh@google.com Delete obsolete thirdPartyPhaseoutCookie functions
2026-05-06 szuend@chromium.org [sdk] Fix flaky CPUThrottlingManager unit tests
2026-05-06 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Roll browser-protocol and CfT

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 chrome-devtools-staff+oncall-change@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:475856190,chromium:500627023,chromium:505974404,chromium:509889343,chromium:510210876
Change-Id: Ibaeefb9016d90147d61fd03502b4391baf564e3f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7819837
Commit-Queue: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1626068}
3 files changed
tree: f008b3b1b71353b74094c1fd39294186311cf6d5
  1. .agents/
  2. .claude/
  3. .gemini/
  4. .github/
  5. agents/
  6. android_webview/
  7. apps/
  8. ash/
  9. base/
  10. build/
  11. build_overrides/
  12. buildtools/
  13. cc/
  14. chrome/
  15. chromecast/
  16. chromeos/
  17. codelabs/
  18. components/
  19. content/
  20. crypto/
  21. dbus/
  22. device/
  23. docs/
  24. extensions/
  25. fuchsia_web/
  26. gin/
  27. google_apis/
  28. gpu/
  29. headless/
  30. infra/
  31. ios/
  32. ipc/
  33. media/
  34. mojo/
  35. net/
  36. pdf/
  37. printing/
  38. remoting/
  39. rlz/
  40. sandbox/
  41. services/
  42. skia/
  43. sql/
  44. storage/
  45. styleguide/
  46. testing/
  47. third_party/
  48. tools/
  49. ui/
  50. url/
  51. webkit/
  52. .clang-format
  53. .clang-tidy
  54. .clangd
  55. .cursorignore
  56. .geminiignore
  57. .git-blame-ignore-revs
  58. .gitallowed
  59. .gitattributes
  60. .gitignore
  61. .gitmodules
  62. .gn
  63. .mailmap
  64. .rustfmt.toml
  65. .vpython3
  66. .yapfignore
  67. ATL_OWNERS
  68. AUTHORS
  69. BUILD.gn
  70. CODE_OF_CONDUCT.md
  71. codereview.settings
  72. CPPLINT.cfg
  73. CRYPTO_OWNERS
  74. DEPS
  75. DIR_METADATA
  76. LICENSE
  77. LICENSE.chromium_os
  78. OWNERS
  79. package.json
  80. PRESUBMIT.py
  81. PRESUBMIT_test.py
  82. PRESUBMIT_test_mocks.py
  83. README.md
  84. SECURITY_OWNERS
  85. WATCHLISTS
README.md

Logo Chromium

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.