[go: nahoru, domu]
Google Git
Sign in
chromium / devtools / devtools-frontend / 67352ebfe6a7f8c5706e38d4295bb0812628e36b
commit67352ebfe6a7f8c5706e38d4295bb0812628e36b[log] [tgz]
authorAndres Olivares <andoli@chromium.org>Tue Mar 07 12:40:22 2023
committerDevtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Mar 07 12:42:51 2023
treec3ef425edb08c5f790d925385e7238695ff6be8f
parent27d82aef6155cd7510c4cd339e97449f2445634a [diff]
Revert "[RPP] Use the new engine in the Timings track"

This reverts commit 27d82aef6155cd7510c4cd339e97449f2445634a.

Reason for revert: Breaking CQ bots

Original change's description:
> [RPP] Use the new engine in the Timings track
>
> NOTE: This has to be landed *after* the new engine has been reenabled
>
> The first track appender is introduced to add the Timings track into the flame chart data (TimingsTrackAppender).
>
> This appender consists of the bits previously in the TimelineFlameChartDataProvider that were in charge of appending the data of the track along with the bits that provided extra feature for events in the track (like stylings and display names).
>
> All these parts are moved to a common place to handle the details of the track together in the same module, but separate from other tracks. The source of data used by the track appender is the output of the new engine
>
> In the future further test coverage will be added using dedicated screenshot tests.
>
> Bug: 1409044
> Change-Id: I007d5ffd93e310cba26546fa09829e02e3cc581c
> Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4295982
> Commit-Queue: Andres Olivares <andoli@chromium.org>
> Reviewed-by: Jack Franklin <jacktfranklin@chromium.org>

Bug: 1409044
Change-Id: Ie9dd0d16351beb996de5d70dba2107c99296b4dc
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4315943
Commit-Queue: Andres Olivares <andoli@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
17 files changed
tree: c3ef425edb08c5f790d925385e7238695ff6be8f
  1. .vscode/
  2. build_overrides/
  3. config/
  4. docs/
  5. extension-api/
  6. front_end/
  7. inspector_overlay/
  8. node_modules/
  9. scripts/
  10. test/
  11. third_party/
  12. v8/
  13. .clang-format
  14. .editorconfig
  15. .eslintignore
  16. .eslintrc.js
  17. .git-blame-ignore-revs
  18. .gitattributes
  19. .gitignore
  20. .gn
  21. .mailmap
  22. .npmignore
  23. .npmrc
  24. .style.yapf
  25. .stylelintignore
  26. .stylelintrc.json
  27. AUTHORS
  28. BUILD.gn
  29. codereview.settings
  30. DEPS
  31. LICENSE
  32. OWNERS
  33. package-lock.json
  34. package.json
  35. PRESUBMIT.py
  36. README.md
  37. tsconfig.json
  38. WATCHLISTS
README.md

Chrome DevTools frontend

npm package

The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.

Source code

The frontend is available on chromium.googlesource.com.

Project documentation

Check out the project documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.

Additional references

Source mirrors

DevTools frontend repository is mirrored on GitHub.

DevTools frontend is also available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES modules, so consuming this package in other tools may require some effort.

The version number of the npm package (e.g. 1.0.373466) refers to the Chromium commit position of latest frontend git commit. It's incremented with every Chromium commit, however the package is updated roughly daily.

Getting in touch