Moving with the keyboard suggestion

I was recently playing a game and I was trying out the new feature of inputting moves with the keyboard. I intended to play Be3, but due to the unfortunate placement of the "3" key being just above the "e" key on my qwerty keyboard, I ended up typing "b3" and made an epic blunder as a result. I realized the error as soon as I typed it, however, there was no way to make a correction before submitting the move since my input was accepted and played instantly.

My suggestion is to add an option to press "enter" before having the keyboard input accepted and played on the board. This way, players could avoid playing a blunder when a typo is made.

This experience also raised a question in my mind. In my limited experience with this new feature (which I think is awesome btw!), the user input is accepted as soon as it is recognized as a legal move. Suppose there is a position where the player to move can castle both short and long and wants to castle long. One would type "O-O-O" to do this but since typing "O-O" is required as part of that, would this input make you castle short automatically?

Here's the relevant part of the code:
github.com/ornicar/lila/blob/master/public/javascripts/keyboardMove.js#L9-L25

So there's a specific exception for the case where you've typed "O-O" but "O-O-O" is in the list of legal moves (line 13), but otherwise it'll immediately parse your move and submit it if it's in the legal move list.

I don't suppose it would be too hard to override this behaviour with a userscript, but I'm not sure if messing with this particular area would trigger Lichess' cheating detection. @thibault, do you have any guidance on whether this is okay or not?

that should be fine.

I've always thought the benefit of being able to type the moves was that you could double-check before hitting enter. Having it instantly go through defeats that entirely.