Diagnostics: support Mic Mute and Keyboard Backlight Toggle top-row keys

This should serve as an example CL for how to add support for new top
row keys to the tester.

The HID usage codes in input_data_provider_keyboard.cc were found in the
action_key array in CrOS EC's usb_hid_keyboard.c [0], while scan codes
can be found from running evtest on a DUT, choosing the keyboard,
pressing the key, and checking the value of MSC_SCAN.

I imported the icons into Inkscape from Illustrator files, then removed
extra markup using the XML Editor, and scaled them to fit in 20px. (For
consistency with the other top-row icons that don't fill their 20px
squares, this meant setting the page size to 20x20px, scaling the icon
to 16px, and centering it on the page.) The Apply Transforms plugin [1]
was then used to apply SVG transforms to the path pixel values
themselves, resulting in the <path> elements that could then be added to
keyboard_icons.html. (Visual designers may have a better workflow for
exporting clean SVGs.)

Screenshot (made with fake data putting both icons on the same top row):
http://shortn/_1tGuUfgQAb

[0]: https://source.chromium.org/chromiumos/chromiumos/codesearch/+/main:src/platform/ec/chip/stm32/usb_hid_keyboard.c?q=%22struct%20action_key_config%20action_key%22
[1]: https://github.com/Klowner/inkscape-applytransforms

Change-Id: Iadfbff172014d2471e6a2ec1854784495e766167
Bug: 1207678
Test: open the tester on a device with the keys on its top row, check
Test: the icon appears correctly and is described properly by ChromeVox.
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3564071
Reviewed-by: Jimmy Gong <jimmyxgong@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Harry Cutts <hcutts@chromium.org>
Cr-Commit-Position: refs/heads/main@{#991674}
9 files changed
tree: 52d1b02d1fa8cda95971d3698ad7e898db1fe754
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython
  61. .vpython3
  62. .yapfignore
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. ENG_REVIEW_OWNERS
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure .

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.