[go: nahoru, domu]
Google Git
Sign in
chromium / devtools / devtools-frontend / 5cc23747aef9bf9380fc09e45897f49295026801
commit5cc23747aef9bf9380fc09e45897f49295026801[log] [tgz]
authorJecelyn Yeen <jec@google.com>Tue Aug 01 13:12:41 2023
committerDevtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Aug 01 14:18:33 2023
tree2b1d0757e4d7e2a6592a5e160abd110334397727
parentaf54bd1f7ddd3098f53649e0e4adebbef4286e09 [diff]
[Override] Improve local override UX in the Network panel

- Rename "Save for overrides" to "Override content"
- Group both overrides menu under same section
- Always show "Override content" in all scenarios
   - before user setup overrides (we will prompt for setup)
   - when user disable overrides (we will enable it automatically)
   - after user overrides the file (we will open the overridden file)

Prior to this change, we only show "Save for overrides" if:
- user has setup overrides before in the Sources panel && never override the selected network resource before

Screenshot: https://crbug.com/1465785#c2

Bug:1465785
Change-Id: I1182a23598484112626fbd0fae9d8fe71edf7a28
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4693563
Commit-Queue: Jecelyn Yeen <jec@chromium.org>
Reviewed-by: Danil Somsikov <dsv@chromium.org>
Reviewed-by: Wolfgang Beyer <wolfi@chromium.org>
7 files changed
tree: 2b1d0757e4d7e2a6592a5e160abd110334397727
  1. .vscode/
  2. build_overrides/
  3. config/
  4. docs/
  5. extension-api/
  6. extensions/
  7. front_end/
  8. inspector_overlay/
  9. node_modules/
  10. scripts/
  11. test/
  12. third_party/
  13. v8/
  14. .clang-format
  15. .editorconfig
  16. .eslintignore
  17. .eslintrc.js
  18. .git-blame-ignore-revs
  19. .gitattributes
  20. .gitignore
  21. .gn
  22. .mailmap
  23. .npmignore
  24. .npmrc
  25. .style.yapf
  26. .stylelintignore
  27. .stylelintrc.json
  28. AUTHORS
  29. BUILD.gn
  30. codereview.settings
  31. DEPS
  32. LICENSE
  33. OWNERS
  34. package-lock.json
  35. package.json
  36. PRESUBMIT.py
  37. README.md
  38. tsconfig.json
  39. 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