Preparation for change of behaviour

While taking a screenshot of viewport we call CDP with
beyondviewport = false because if we were to call with no clip
and beyondviewport = true, after the change of the behaviour in CDP, we would have a fullpage screenshot.

Viewport screenshot goes through the part that is commented to be deleted, to show that it would work with CDP change.
We cannot create a final change of behaviour right now because we are still waiting for CDP change.

Design Doc: https://docs.google.com/document/d/11Dwvy3UuGaFdBxE-nWzVG-oDSQTvEyomu42SN3dCpRs/edit#heading=h.8btw5sz9igs9
Related CL(s): https://chromium-review.googlesource.com/c/chromium/src/+/3797208

Bug: chromium:1357584
Change-Id: I01f78ac0269b7428c923e1292817e8a58bac3242
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3838171
Reviewed-by: Arkadia Kowalczyk <arkadiak@google.com>
Commit-Queue: Arkadia Kowalczyk <arkadiak@google.com>
Reviewed-by: Mathias Bynens <mathias@chromium.org>
2 files changed
tree: fd14ebaacdb1d68ad3ddc3fc0ecfc2e219e1d602
  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. .gitattributes
  18. .gitignore
  19. .gn
  20. .mailmap
  21. .npmignore
  22. .npmrc
  23. .style.yapf
  24. .stylelintignore
  25. .stylelintrc.json
  26. ARCHITECTURE.md
  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.

Design guidelines

Please be aware that DevTools follows additional development guidelines.

Issue triage

The issue triage guidelines can be found in docs/triage_guidelines.md.

Workflows

Instructions to set up, use, and maintain a DevTools frontend checkout can be found in docs/workflows.md.

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