Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closing terminal that was launched from another terminal instance minimizes the parent terminal #14012

Closed
Tracked by #14957
SaadAhmedGit opened this issue Sep 15, 2022 · 2 comments
Labels
Area-DefApp Area-Windowing Window frame, quake mode, tearout Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Priority-2 A description (P2) Product-Terminal The new Windows Terminal.

Comments

@SaadAhmedGit
Copy link

SaadAhmedGit commented Sep 15, 2022

Windows Terminal version

1.15.2525.0

Windows build number

10.0.22000.0 (21H2)

Other Software

No response

Steps to reproduce

  1. Have anyother program opened up (a web browser in my case).
  2. Launch terminal (any terminal app can be used here since I have tested it with VSCode's built-in terminal too)
  3. Click on the icon of the other app that you opened in step 1 from the taskbar. The program should now be on top.
  4. Click on the terminal program that you opened in step 2 from taskbar. The terminal should now be on top.
  5. Type start cmd and hit enter (make sure windows terminal is set as the default terminal)
  6. When the child terminal instance spawns, close it.

Expected Behavior

After closing the child instance, the parent instance should be the one to stay on top.

Actual Behavior

The parent terminal minimizes when we close the child instance and the program that we opened up in step 1 is now on top.

@SaadAhmedGit SaadAhmedGit added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Sep 15, 2022
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Sep 15, 2022
@zadjii-msft zadjii-msft added Product-Terminal The new Windows Terminal. Priority-2 A description (P2) Area-DefApp Area-Windowing Window frame, quake mode, tearout labels Feb 14, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot removed the Needs-Tag-Fix Doesn't match tag requirements label Feb 14, 2023
@carlos-zamora
Copy link
Member

Hi @SaadAhmedGit. Sorry for the delay. Is this still happening for you on the latest Windows Terminal version?

@carlos-zamora carlos-zamora added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Mar 22, 2023
@SaadAhmedGit
Copy link
Author

No problem @carlos-zamora. Unfortunately, I have switched to Linux so I can't test this out on Windows but, iirc, it used to happen on multiple devices and not just on my laptop so if the above steps don't reproduce it, it might have been fixed.

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Mar 22, 2023
@carlos-zamora carlos-zamora closed this as not planned Won't fix, can't repro, duplicate, stale Mar 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-DefApp Area-Windowing Window frame, quake mode, tearout Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Priority-2 A description (P2) Product-Terminal The new Windows Terminal.
Projects
None yet
Development

No branches or pull requests

3 participants