Confusion about the shift modifier and capital letters in the input triggers protocol

[mattkae]

Version

v2.29.0

Environment

N/A

What happened? What did you expect to happen?

Listening on input triggers that include the "Shift" key silently requires that the corresponding input keysym are also capitalized, which is confusing. I would expect that "Shift" + Keysym refers to the lowercase keysym.

Reproduction steps

1. Write a client that tries to bind a global shortcut to "Ctrl" + "Shift" + "s" (lowercase 's'!)
2. Successfully get the binding
3. Click Ctrl + Shift + s and note your clinet never gets triggered
4. Instead, bind to "Ctrl" + "Shift" + "S" (or "Ctrl" + "S") and see that it works!

Relevant log output