Some years ago, I pointed out an interface problem on unintended castling (lichess.org/forum/lichess-feedback/please-disable-the-alternative-way-of-castling#1). Grabbing the K BEFORE the opponent's move and clicking on a R AFTER an unexpected opponent's move, may lead to unintended castling executed.
This problem was corrected on normal chess, but not on Chess960 because moving the K on the R is the only way to castle in Chess960. Please add codes to automatically de-select the pre-selected K when an R on its original square is clicked, which clearly intends a R move, not castling.
This problem was corrected on normal chess, but not on Chess960 because moving the K on the R is the only way to castle in Chess960. Please add codes to automatically de-select the pre-selected K when an R on its original square is clicked, which clearly intends a R move, not castling.
