UI Eng: migrate timeline/components/LayoutShiftDetails

This CL migrates the LayoutShiftDetails component. There's a few
follow-ups which is why I haven't marked the bug as fixed yet:

1. We dispatch regular events on the element; I think we probably want
   to swap to using the Widget's event system. However, this CL already
   felt large to me, so I would rather do that as a distinct follow-up.
2. The code for dealing with toggling the popover and finding the right
   event feels slightly messy to me; I'd like to see if that can be done
   in a cleaner way, but again, in a follow-up.

R=dsv@chromium.org

Bug: 407940635
Change-Id: I3851c7de28fe44aa2f3ef9d56211e32cac825166
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6768732
Reviewed-by: Danil Somsikov <dsv@chromium.org>
Auto-Submit: Jack Franklin <jacktfranklin@chromium.org>
Commit-Queue: Danil Somsikov <dsv@chromium.org>
Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
5 files changed
tree: b2fae4475fb188330914df782e674cc80ae6a1f0
  1. .github/
  2. .vscode/
  3. build_overrides/
  4. config/
  5. docs/
  6. extension-api/
  7. extensions/
  8. front_end/
  9. inspector_overlay/
  10. node_modules/
  11. scripts/
  12. test/
  13. third_party/
  14. v8/
  15. .clang-format
  16. .clang-format-ignore
  17. .editorconfig
  18. .git-blame-ignore-revs
  19. .gitallowed
  20. .gitattributes
  21. .gitignore
  22. .gitmodules
  23. .gn
  24. .mailmap
  25. .npmignore
  26. .npmrc
  27. .style.yapf
  28. .stylelintignore
  29. .stylelintrc.json
  30. AUTHORS
  31. BUILD.gn
  32. codereview.settings
  33. CONTRIBUTING.md
  34. DEPS
  35. DIR_METADATA
  36. eslint.config.mjs
  37. favicon.ico
  38. LICENSE
  39. OWNERS
  40. package-lock.json
  41. package.json
  42. PRESUBMIT.py
  43. README.md
  44. WATCHLISTS
README.md

Chrome DevTools frontend

npm package

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

Source code and documentation

The frontend is available on chromium.googlesource.com. Check out the Chromium DevTools documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.

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

There are a few options to keep an eye on the latest and greatest of DevTools development: