shortcuts: Add replacement key_display for shortcuts missing key_display

This CL fixes the blank keys in the app (see screenshots below for
examples) caused by missing key_display values.

Screenshot 1 Before: https://screenshot.googleplex.com/A4jL5m7WMhZ4gDA
Screenshot 1 After: https://screenshot.googleplex.com/5xXUtfaUAMP594D
Screenshot 2 Before: https://screenshot.googleplex.com/4mxtzyMEScj86xM
Screenshot 2 After: https://screenshot.googleplex.com/7tzYt5JhvRF2ZVW

These empty key_display values occur when the function
`KeycodeToKeyString` returns an empty string for a given key_code. To
work around this without affecting other consumers of that function,
I've added a map with key_display values for the missing keys.

These key_display values will ultimately be turned into icons by the
frontend. For example, MicrophoneMuteToggle is rendered as an icon in
screenshot 2. The other keys will be replaced with icons in future CLs
once we get the SVGs from Design.

Below is a file-by-file explanation.

In accelerator_configuration_provider.h, I move
GetKeyDisplay so that it's public and therefore visible to
the test. I also move CreateAcceleratorInfo from the anonymous
namespace to a private method on the provider.

In accelerator_configuration_provider.cc, I add the lookup map and
GetKeyDisplay function. Note that GetKeyDisplayMap returns a static map
to work around the fact that strings cannot be part of constexprs.
I also move CreateAcceleratorInfo from the anonymous namespace to the
provider.

In acceleration_configuration_provider_unittest.cc, I add tests for
GetKeyDisplay.

Bug: b/216049298
Test: browser_tests --gtest_filter=ShortcutCustomizationApp*
Change-Id: Id4940f00a175cab9c60d3bc28688e4b426b9357b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4083841
Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org>
Commit-Queue: Camden Bickel <cambickel@google.com>
Cr-Commit-Position: refs/heads/main@{#1082672}
3 files changed
tree: 2057fb64d309fe91f950a93b5478a06480ce324a
  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_web/
  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. .vpython3
  61. .yapfignore
  62. AUTHORS
  63. BUILD.gn
  64. CODE_OF_CONDUCT.md
  65. codereview.settings
  66. DEPS
  67. DIR_METADATA
  68. ENG_REVIEW_OWNERS
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. 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.