Hey, thanks for sharing this!

Yeah, I can confirm this behavior as well—DisplayName in WebGL builds seems to return the key as mapped on the QWERTY layout, not based on the OS-level keyboard layout. So when you're using a Cyrillic layout and press "g", it still returns "g" instead of "п".

It looks like WebGL's input system relies on the underlying JavaScript KeyboardEvent.code or key, which is tied to the physical key rather than the character mapped in the OS layout. That’s probably why it behaves differently compared to native platforms.

We encountered a similar limitation when developing a multilingual chat interface for a mobile app development company in Dubai—to support localized input in WebGL, we had to capture raw key events at the browser level using a JavaScript plugin and pass that into Unity via SendMessage().

So unless Unity changes how WebGL input works or gives more flexibility, a workaround could be custom JS to fetch KeyboardEvent.key and forward it into Unity.

Let me know if you’d like help setting up a basic plugin for that!