"Attach to the most recently used window on this desktop" continues to open in instance on other desktop

[rkhoury]

Windows Terminal version

1.24.250228001-llm

Windows build number

10.0.26100

Other Software

No response

Steps to reproduce

1. Modify the Startup setting New instance behavior and set the value to Attach to the most recently used window on this desktop
2. Create a new Terminal (or Terminal Preview) instance on Desktop 1.
3. Create a new Terminal instance on Desktop 2 - for me this changes desktops and launches the instance on Desktop 1.

Note (implied): my Terminal desktop settings are not set to "Show windows from this app on all desktops" so I can attempt to keep terminal instances aligned with particular work streams.

Reproduces in release build 1.23.10353.0 or canary build version 1.24.250228001-llm

Expected Behavior

When on a new desktop I expect a new instance of Terminal (or Terminal Preview) to create a new window and attach to that.

Actual Behavior

Assuming an instance of Terminal is already running on another desktop to the one I'm currently on, creating a new Terminal instance moves me to the other desktop.

[similar-issues-ai]

We've found some similar issues:

• New instance behavior doesn't work as expected with multiple monitors #14130 , similarity score: 82%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

[rkhoury]

We've found some similar issues:

• New instance behavior doesn't work as expected with multiple monitors #14130 , similarity score: 82%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

The other issue looks similar but appears to be related to other monitors rather than virtual desktops - at least from what I could see. I'm not sure if responding with 👎 was the right thing to do?

[DHowett]

It was! Thanks!

We may have broken this in the small big medium-sized windowing refactoring we did in #18215.