entered value: Shift + A
expected: KeyEvent { key: Char('A'), modifiers: SHIFT}

Shift-A sends only A with no shift modifier key in the standard keyboard encoding, so we don't know if SHIFT was actually pressed in order to produce that input: it's very difficult to make that kind of determination unless you know the active keyboard layout on the user's machine, and that may not even be local to the system where your console application is running.

Same goes for :.

entered value: Control + j
result: KeyEvent { key: Enter, modifiers: NONE }

Control-<alpha> is delivered as a control code in the standard key encoding, so CTRL-J is indistinguishable from Enter, CTRL-H is backspace and so on. These are famously ambiguous sequences to map in an application. https://wezfurlong.org/wezterm/config/key-encoding.html has more background on this.

termwiz could request modifyOtherKeys to resolve this for terminals that respect that sequence (42f855d does that. There might need to be something different done for windows terminals), but it's worth noting that there is no 100% perfect cross platform way to unambiguously differentiate those key presses: there will always be someone that is going to hit this.

Shift-Tab

Thanks; fixed in 42f855d

is it normal that ColorAttribute::TrueColorWithPaletteFallback() never works (always returns black) ? I can't get it to show the colors when converting rgb to rgbatuple, only the ansi colors works.

If wezterm doesn't think the terminal supports 24-bit color, then it will use the palette fallback.
Going to need more info on the environment to understand whether that is working correctly.

Thanks wez, I understand a little more how it works, as for the rgb colors, I find it strange, because the terminal is truecolor, when testing with crossterm, it gives me back the rgb colors without problems, but in termwiz I use:

Change::Attribute(AttributeChange::Foreground(
    ColorAttribute::TrueColorWithPaletteFallback(
        RgbColor::new_8bpc(color.0, color.1, color.2).to_tuple_rgba(),
        AnsiColor::Blue.into(),
    ),
)),

but neither the blue color returns me in case of failure.

Crossterm:	Termwiz:

The indexed color stuff is potentially related to:

• termwiz: default SGR 8 bit color encoding doesn't work in PowerShell #2723