@wi-fr commented in #4110 that the desired behavior may have not been implemented properly in the new user input processor. This issue will track reproducing and fixing this issue.