Steam client version (build number or date): 1682708537
Distribution (e.g. Ubuntu): Arch Linux
Opted into Steam client beta?: [Yes/No] No
Please describe your issue in as much detail as possible:
If the user enables Family View (FV) and sets its state to on, then uses a Steam browser protocol command to open the console, it is blocked. If the user immediately sets the state of FV to off and issues the same browser protocol command, the console remains blocked until the user explicitly navigates to a different page and then back to the console.
Steps for reproducing this issue:
Enable FV via the settings menu
Start on some page of the client, such as the largegameslist
Toggle FV to on by clicking the icon (turns green)
Issue steam://open/console
The Steam client is raised and focused but the console is blocked due to the lowered permission level
Immediately toggle FV to off by clicking the icon (turns red)
Issue the same steam://open/console command
The Steam client is raised and focused, but remains on the last permissible page that was not the console (in this example, largegameslist)
You can continue issuing console open commands, but the console will not open
Issue another command, such as steam://open/largegameslist (it can be the same as the current page), or some manual invocation through the client, to change the page
Issue steam://open/console again, and this time it works.
It appears as though the "blocked" state from when FV's state is on is being remembered by the client even after turning FV off, and this state is not cleared unless the user explicitly navigates away from the page before attempting to launch the console. From the point of view of the user, this is seen:
I am on the largegameslist.
FV is on and I try to open the console, but I am blocked. I remain on the largegameslist
FV is off and I try to open the console, but I remain on the largegameslist.
This causes the console open command to appear to be doing nothing, despite the elevated privileges impied by FV state == OFF.
Your system information
Please describe your issue in as much detail as possible:
If the user enables Family View (FV) and sets its state to on, then uses a Steam browser protocol command to open the console, it is blocked. If the user immediately sets the state of FV to off and issues the same browser protocol command, the console remains blocked until the user explicitly navigates to a different page and then back to the console.
Steps for reproducing this issue:
steam://open/consolesteam://open/consolecommandsteam://open/largegameslist(it can be the same as the current page), or some manual invocation through the client, to change the pagesteam://open/consoleagain, and this time it works.It appears as though the "blocked" state from when FV's state is on is being remembered by the client even after turning FV off, and this state is not cleared unless the user explicitly navigates away from the page before attempting to launch the console. From the point of view of the user, this is seen:
This causes the console open command to appear to be doing nothing, despite the elevated privileges impied by FV state == OFF.