Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[General] - Remote Play's Authorize Device prompt does not trigger the on-screen keyboard. #11495

Open
ZereoX opened this issue Nov 19, 2024 · 0 comments

Comments

@ZereoX
Copy link

ZereoX commented Nov 19, 2024

Your system information

  • Steam client version (build number or date): 1731433018 (Stable) / 1731990050 (Beta)
  • Distribution (e.g. Ubuntu): SteamOS 3.6.20 / 3.7.0 (Deck) and Manjaro w/ Gnome 46 (Desktop)
  • Opted into Steam client beta?: Yes. Issue is present on both Stable and Beta
  • Have you checked for system updates?: Yes
  • Steam Logs: steam-logs.tar.gz
  • GPU: AMD Van Gogh RDNA 2.0 (Steam Deck) and RX 7800XT (Desktop)

Please describe your issue in as much detail as possible:

When prompted to enter an authorization code when using Remote Play from a new device, the field appears to be highlighted (i.e. visible blinking I-beam), but the on-screen keyboard (OSK) does not open automatically. User must manually press A to invoke it.

This behaviour is also present with Steam Guard Code and the Steam Login screen however those screen present the user with additional options which would be obfuscated by automatically opening the on-screen keyboard. The Authorize Device prompt only offers the option to enter a code.

Remote Play Authorization Code
Streaming_To

Steps for reproducing this issue:

  1. Navigate to a title that is installed on a remote computer.
  2. Select the dropdown menu near the Install / Play button and select the remote computer.
  3. Press Stream

Reproduction Rate: 5/5

Affected Platforms

  • LCD / Jupiter: Yes
  • OLED / Galileo: Yes
  • Desktop Deck-like session (gamescope -e -- steam -gamepadui -steamdeck): Yes
  • Desktop: Yes, in Big Picture Mode

Actual result

  • On-screen keyboard is not automatically invoked on the Authorize Device prompt.

Expected result

  • On-screen keyboard is automatically invoked on the Authorize Device prompt.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants