Link to problematic headers from CORS issues

This CL reveals problematic headers when clicking on the request links
in CORS issues. This makes it easier to understand what the problem is,
and quicker to identify misconfigured header values.

Drive-by: Whitespace fix in corsHeaderDisallowedByPreflightResponse.md

Screenshot: https://imgur.com/a/3biLKTJ
Bug: chromium:1141824
Change-Id: I65f54ee2a608375eacdbdbcd49642eb4d49cd3cc
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2866387
Reviewed-by: Wolfgang Beyer <wolfi@chromium.org>
Commit-Queue: Sigurd Schneider <sigurds@chromium.org>
3 files changed
tree: 36e8466b6fa010b72827a0197b39df9aff15b864
  1. build_overrides/
  2. config/
  3. docs/
  4. front_end/
  5. inspector_overlay/
  6. node_modules/
  7. scripts/
  8. test/
  9. third_party/
  10. v8/
  11. .clang-format
  12. .editorconfig
  13. .eslintignore
  14. .eslintrc.js
  15. .gitattributes
  16. .gitignore
  17. .gn
  18. .npmignore
  19. .npmrc
  20. .style.yapf
  21. .stylelintignore
  22. .stylelintrc.json
  23. ARCHITECTURE.md
  24. AUTHORS
  25. BUILD.gn
  26. DEPS
  27. LICENSE
  28. OWNERS
  29. package-lock.json
  30. package.json
  31. PRESUBMIT.py
  32. README.md
  33. tsconfig.base.json
  34. tsconfig.json
  35. 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