Autocorrect broken :: Steam Client Beta

STEAM GROUP

Steam Client Beta SteamBeta

Join Group

STEAM GROUP

Steam Client Beta SteamBeta

399,703
MEMBERS

15,479

IN-GAME

96,855

ONLINE

Founded

8 January, 2013

Overview Announcements Discussions Events Members Comments

All Discussions > Bug Reports > Topic Details

IFIYGD 13 Sep @ 2:00am

Autocorrect broken

ISSUE
Autocorrect displays a drop down menu of options for misspelled words, but does no substitute the options when clicked upon. Also "Add to dictionary" is unresponsive and foes not add a new word to the autocorrect dictionary.

OS
Windows 10 v. 22H2 64 bit

STEAM CLIENT VERSION
Steam Beta Branch: Stable Client
Steam Version: 1757650573
Steam Client Build Date: Fri, Sep 12 00:57 UTC -08:00
Steam Web Build Date: Thu, Sep 11 19:47 UTC -08:00
Steam API Version: SteamClient022

STEPS
Have a misspelled or unrecognized word show a red zigzag line underneath.
Right click to open the autocorrect drop down options menu.
Select the correctly spelled word or select "Add to dictionary" and click.
Click multiple times while the autocorrect options menu remains unresponsive and curse under your breath a few dozen times.

EXPECTED
Clicking on the correct spelling of a word or the "Add to dictionary" option actually does something.

I first noticed this behavior just after this past Tuesday's weekly server maintenance, behavior did not change after the small client update I received last night.

< >

Showing 1-4 of 4 comments

cSg|mc-Hotsauce 13 Sep @ 8:01am

Yeah. It was broken in the beta for a while and I guess it got into the mainline branch when that was recently updated.

IFIYGD 13 Sep @ 9:20am

Originally posted by cSg|mc-Hotsauce:
Yeah. It was broken in the beta for a while and I guess it got into the mainline branch when that was recently updated.

:nkCool:

Yeah, I am not sure if the Stable Client update adding Accessibility options to settings happened at the same time, since I don't actively opt into Beta Client these days to keep track of when things get shipped from Beta > Stable. But it seems a bit ironic if the changes coincided- adding new Accessibility features removed one very useful one that we had before.