Bug: Broken inline code when using the German keyboard

[olafsulich]

Lexical version:

v0.23.0

Steps To Reproduce

1. Switch your keyboard to the German one
2. Type one backtick, add text, add the second backtick
3. Instead of creating an inline code node, nothing happens
4. Press double space, and then backspace
5. Only after that, the code turns into the inline code node

Screen.Recording.2025-01-08.at.12.02.34.mov

With the German keyboard and the backticks, we can create some symbols, an example:

Screen.Recording.2025-01-08.at.12.18.28.mov

So if I press the backtick and the "a" character, it creates the "à" symbol. I can reject it by pressing the space bar, and then I get the normal "`a".

That's why I have to press the space bar twice to create a space after the inline code - once to reject the "transformation", and once to create the space itself.

The current behavior

To create an inline code block, I have to press the space bar twice, and then the backspace button.

The expected behavior

Creating the inline code block works after rejecting the "transformation", which means hitting the space bar once.

I have tried rich text editors in Slack and Jira, both are handling it this way.

Impact of fix

It's a minor issue, but one that could be frustrating for those using the German keyboard.

[etrepum]

This has to do with markdown shortcuts, I suppose it will need some extra handling for composition events