Jeffen Nilsson
124 discussion posts
Attached is a gif of the issue with firefox and plexamp.
This issue also happens with mpv, chromium, and Plex
these are my settings for the trigger firefox
and the trigger settings for plexamp
I'm on version 11.1.1 but i've noticed this issue for a couple of weeks so its possible its back a couple versions where the restored trigger mightve been changed.
• Attachment [protected]: firefox_sThxRCqs3w.gif [12,509,798 bytes]
• Attachment [protected]: Plexamp_46kccX4gEt.gif [5,941,675 bytes]
I tested this out here but I can't seem to reproduce it. Do you have any other triggers that would fire on this window? I wonder if the "Stop processing.." setting isn't working and two triggers are fighting over eachother
Jeffen Nilsson
124 discussion posts
I have both a trigger for created, focused, and restored.
Disabling all triggers except for restored does NOT fix the issue.
Jeffen Nilsson
124 discussion posts
I noticed that the issue does not occur if the window is in a different spot ie if i set the window to windowwed mode and move it to a different monitor and THEN minimize and restore the window - it works as it should.
However if the window is already in the target location and i do a minimize and restore THEN the issue happens
• Attachment [protected]: 20250312_165232.mp4 [33,343,080 bytes]
Jeffen Nilsson
124 discussion posts
this should be it, it should be just after 00:01
• Attachment [protected]: DisplayFusionDebugInfo.zip [255,694 bytes]
Thanks! I was able to reproduce this issue here and have added it to our list to fix up. Meantime, if you disable the "Maximized" checkbox in the "specific size/location" action in the Trigger, it will prevent that from happening, with the caveat that the window won't actually get maximized when the Trigger runs. The window will still size to the full size of the monitor though.
