Doubled Input for Chat on Linux/Steamdeck

[Civilianpig]

Checklist

• [x] I've checked both open and recently closed issues to ensure this issue is not already reported.
• [x] I am using the newest version of TETR.IO.
• [x] I am using a supported browser or the Desktop Client.
• [x] I am not using anything that modifies game code (e.g. TETR.IO PLUS).
• [x] I am certain this is a bug, not a feature request.

OS and Version

SteamOS 3.7.15

Browser and version

Official desktop client (.Tar.gz v 1.7.5)

Describe the bug/issue

I am running the official Tar.gz release on steam deck in gaming mode. I hope this is in scope here, if not feel free to remove.

Gameplay behaves normally for the most part, the issue only presents when the chat is focused. All keypresses in the chat are sent twice, e.g.,

• 'gg' > 'gggg'
• 'glhf' > 'ggllhhff'

This happens whether or not steam input is enabled, but does not happen in desktop mode. It happens with the on-screen keyboard, with a physical bluetooth keyboard, and even with controller buttons mapped to keyboard inputs via steam input. It is not intermittent, every single text input is doubled.

Thanks in advance for any help.

Reproducing

Type any text in the chat box in game mode.

Expected behavior

Each keypress to be entered one time.

Screenshots

No response

Console logs

No response

Additional context

No response

[kcfresh53]

I can second this issue, and provide a little more insight on the issue (I am a game developer that ran into this issue earlier last year). The double input is related to steam input. You can mitigate this by turning off steam input for the game.

For an actual fix, it depends. I am aware that the game is using electron, but that's the extent of the tech stack that I am familiar with. The issue could be as low level as the windowing/ input library (versions of SDL2 have this issue), or some integration of steam input in the main binary could be the solution.

[Civilianpig]

Thanks for your insight. I had tested turning on/off steam input and it didn't change the issue even though that was the best answer I could find. I actually have managed to resolve it now by changing the compatibility layer to one of the older steam runtime ones (not proton obviously). I don't have the exact version right now but I can comment it later. It now works as normal even with steam input enabled.