XWayland output reference stuck on wrong/inactive display, breaking mouse click input for fullscreen Proton game (Black Ops 3)

[derpy256]

Running Call of Duty: Black Ops III (Steam, via Proton) on a dual-monitor setup. Experiencing a persistent issue where mouse motion is captured correctly in-game (camera look works), but mouse clicks/buttons do not register at all in the game's main menu and pause menu — including left click, right click, and additional mouse buttons.

Diagnostic steps taken:

Ran cosmic-randr list while BO3 was actively running. Output showed the xwayland field as false on my right monitor (the active display running the game) and true on my left monitor (secondary display).
Disabled the left monitor entirely via Settings → Displays → Enable/Disable toggle. Relaunched BO3 — issue persisted identically. Re-ran cosmic-randr list: xwayland still showed false on the only active output.
Fully logged out and back in with the left monitor still disabled, to force a clean XWayland session state. Relaunched BO3 — no change. xwayland field still false on the sole active display.
Tried mirroring displays instead of disabling — same or worse behavior (complete mouse input loss).
Attempted to identify a "Primary display" setting to test whether XWayland's reference output ties to that — no such option currently exposed in Settings → Displays on my COSMIC version.

Expected behavior: XWayland's active/reference output should match the display the fullscreen game window is actually rendering on, especially when only one output is active, and mouse click events should route correctly to the focused game window regardless of monitor configuration.

Actual behavior: xwayland field remains false on the only active output even after disabling the second monitor and restarting the session. Mouse motion is captured but click/button events are not delivered to the game window in menus, specifically for this older DirectInput-style title.

Additional context: This may be related to two other open issues I found — #475 ("Fullscreen games running in xwayland become non-functional once focus is lost") and #489 ("[Game] Hunt Showdown gets ignored by the compositor"). Modern titles (Cyberpunk 2077, Elden Ring) do not exhibit this issue on the same setup, suggesting it's specific to how legacy XWayland/DirectInput-style input handling interacts with cosmic-comp's output/focus management.
Output for cosmic-randr list:
DP-1 (enabled)
Make: LG Electronics
Model: LG ULTRAGEAR
Physical Size: 600 x 340 mm
Position: 2560,0
Scale: 100%
Transform: normal
Adaptive Sync Support: true
Adaptive Sync: automatic
Xwayland primary: false

Modes:
2560x1440 @ 119.998 Hz (current) (preferred)
2560x1440 @ 99.946 Hz
2560x1440 @ 59.951 Hz
1920x1080 @ 74.906 Hz
1920x1080 @ 60.000 Hz
1920x1080 @ 59.939 Hz
1920x1080 @ 50.000 Hz
1680x1050 @ 59.954 Hz
1600x900 @ 60.000 Hz
1280x1024 @ 75.025 Hz
1280x1024 @ 60.020 Hz
1280x800 @ 59.810 Hz
1280x720 @ 60.000 Hz
1280x720 @ 59.943 Hz
1280x720 @ 50.000 Hz
1152x864 @ 59.959 Hz
1024x768 @ 75.029 Hz
1024x768 @ 60.004 Hz
800x600 @ 75.000 Hz
800x600 @ 60.317 Hz
720x480 @ 59.940 Hz
640x480 @ 75.000 Hz
640x480 @ 59.940 Hz
640x480 @ 59.929 Hz
HDMI-A-1 (enabled)
Make: LG Electronics
Model: LG ULTRAGEAR
Physical Size: 600 x 340 mm
Position: 0,0
Scale: 100%
Transform: normal
Adaptive Sync Support: false
Adaptive Sync: false
Xwayland primary: false

Modes:
3840x2160 @ 59.940 Hz
3840x2160 @ 50.000 Hz
3840x2160 @ 29.970 Hz
3840x2160 @ 25.000 Hz
3840x2160 @ 23.976 Hz
2560x1440 @ 99.946 Hz (current) (preferred)
2560x1440 @ 74.971 Hz
2560x1440 @ 59.951 Hz
1920x1080 @ 119.879 Hz
1920x1080 @ 75.001 Hz
1920x1080 @ 60.000 Hz
1920x1080 @ 59.939 Hz
1920x1080 @ 50.000 Hz
1680x1050 @ 59.954 Hz
1600x900 @ 60.000 Hz
1280x1024 @ 75.025 Hz
1280x1024 @ 60.020 Hz
1280x800 @ 59.810 Hz
1280x720 @ 60.000 Hz
1280x720 @ 59.943 Hz
1280x720 @ 50.000 Hz
1152x864 @ 59.997 Hz
1024x768 @ 75.029 Hz
1024x768 @ 60.004 Hz
800x600 @ 75.000 Hz
800x600 @ 60.317 Hz
720x576 @ 50.000 Hz
720x480 @ 59.940 Hz
640x480 @ 75.000 Hz
640x480 @ 59.940 Hz
640x480 @ 59.929 Hz
OS version:
Pop!_OS 24.04 LTS COSMIC
GPU and Driver:
lspci -k | grep -A 3 VGA
01:00.0 VGA compatible controller: NVIDIA Corporation AD103 [GeForce RTX 4080] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd AD103 [GeForce RTX 4080]
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia

0f:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raphael (rev cb)
Subsystem: ASRock Incorporation Raphael
Kernel driver in use: amdgpu
Kernel modules: amdgpu
COSMIC Version
cosmic-comp:
Installed: 0.1179011874824.040fbd457
Candidate: 0.1179011874824.040fbd457
Version table:
*** 0.1179011874824.04~0fbd457 1001
1001 http://apt.pop-os.org/release noble/main amd64 Packages
100 /var/lib/dpkg/status

[Sisyphus1813]

I've had this same issue for an extended period of time. For me, using hotkeys to move the window to a separate display and then back to the original display fixes the issue (observed on Helldivers, BO3, some indie titles), though I have not looked at any logs.

[derpy256]

I tried to no avail, the only fix for me that worked was to disable my second display and even then it was iffy. I tried installing a KDE plasma desktop environment and that fixed the issue.