protonscr

[Big Picture Mode] Store Search Content Filtering Dialogue Window is Innaccessible via Controller

steamopen Big PictureDistro Family: GentooGeneral controller / Steam InputWeb Component
ValveSoftware/steam-for-linux#11875 · opened 2025-04-03 by ThisNekoGuy · updated 2025-04-11 · 0 comments · github
TThisNekoGuy 2025-04-03 github

Your system information

  • Steam client version (build number or date): 1743554648
  • Distribution: Gentoo (LLVM)
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes
  • Steam Logs: steam-logs.tar.gz
  • GPU: AMD RX 7800 XT

Please describe your issue in as much detail as possible:

When navigating to the Store page in Big Picture Mode, navigating to the content filtering box (the little settings cog above the search results list) on a controller and opening it doesn't focus to that new dialogue properly. Specifically: the controller movement doesn't switch to the new window, it remains controllable on the search results page in the background and I can't interact with (nor close, unless I leave the search page entirely) the foreground dialogue window to manage what results to see.

Screenshot (click me):

Image

To clarify: this is not the same issue as https://github.com/ValveSoftware/steam-for-linux/issues/11847

Steps for reproducing this issue:

  1. Run Steam in gamescope (This is how I was using Big Picture Mode to force Steam Input to work for some games like Hitman III for use with gamescope) - (The below shows an example, setting Big Picture Mode to 4K)
env ENABLE_GAMESCOPE_WSI=1 gamescope -e --nested-refresh=60 -w 3840 -h 2160 -f -R --rt --force-grab-cursor --hide-cursor-delay 3000 --fade-out-duration 200 --prefer-vk-device --adaptive-sync --hdr-itm-enable --mangoapp -- steam -bigpicture
  1. Press the Steam "guide" button (Controller logo button)
  2. Navigate to "Store"
  3. Select "Search" at the top of the page
  4. Go slightly down (using a controller, of course) to select the content filtering cog button (this of course requires that content filtering is enabled and has values set)
  5. Attempt to interact with it via controller (<- this is the problem)