Add Rendering Shortcuts section in setting for Toggle force Css
preference color shortcut feature

This CL
1. Add "Rendering" Shortcuts section in setting.

2. Add 'Toggle forces CSS prefers-color-scheme color' shortcut feature.
User able to set shortcut, to use it to toggle CSS prefer color scheme



How to test: (video record covered all steps)
1. Go to https://twitter.com/
2. Open devtools -> Settings -> Experiments -> filter "key" word ->
   enable "Enable keyboard shortcut editor"

3. Reload devtools
4. Go to devtools Settings -> Shortcuts -> find "Rendings" secion ->
   set "Toggle force CSS ..." shortcut

5. Execute shortcut and check twitter's UI



screenshots:
- https://imgur.com/a/GCeyVB2

video record
- https://youtu.be/Mx9gqvIzIzU


Bug: 1280398
Change-Id: I9f69a46705d167bc1e1a17f8bfbe3582af8468aa
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3614398
Commit-Queue: Changhao Han <[email protected]>
Reviewed-by: Mathias Bynens <[email protected]>
Reviewed-by: Changhao Han <[email protected]>
6 files changed
tree: 1fa959727fe3eb4141f9dad1f7496ccc25219dc5
  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. DEPS
  30. LICENSE
  31. OWNERS
  32. package-lock.json
  33. package.json
  34. PRESUBMIT.py
  35. README.md
  36. tsconfig.json
  37. 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