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 One Instance of Windows Terminal Closes All Instances When unfocusedAppearance with Opacity 100 is Enabled #17873

Closed
NikoEscobar opened this issue Sep 7, 2024 · 4 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@NikoEscobar
Copy link

Windows Terminal version

1.20.11781.0

Windows build number

10.0.22631.0

Other Software

No response

Steps to reproduce

  1. Open Windows Terminal.

  2. In the settings, set the following configurations:

    {
      "opacity": 40,
      "useAcrylic": true,
      "unfocusedAppearance": {
        "opacity": 100
      }
    }
    
  3. Open multiple instances of Windows Terminal.

  4. Close one of the open instances.

Expected Behavior

Only the closed instance of Windows Terminal should close, leaving the other instances open and unaffected.

Actual Behavior

Closing one instance of Windows Terminal causes all other open instances to close unexpectedly.

@NikoEscobar NikoEscobar added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Sep 7, 2024
@zadjii-msft
Copy link
Member

This sounds a lot like #17520 - can you try Windows Terminal v1.21.2361.0 or Windows Terminal Preview v1.22.2362.0 and see if it's fixed for you there/?

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Sep 9, 2024
@NikoEscobar
Copy link
Author

This sounds a lot like #17520 - can you try Windows Terminal v1.21.2361.0 or Windows Terminal Preview v1.22.2362.0 and see if it's fixed for you there/?

I can confirm the issue is not present on Windows Terminal Preview v1.22.2362.0

As for the Windows Terminal v1.21.2361.0 version, I'm not really sure how to update my current version to this one, Microsoft Store is not detecting new a version to update.

@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 Sep 11, 2024
@carlos-zamora
Copy link
Member

Awesome! Thanks for filing and following up! We'll mark this as a /dup of #17520.

Copy link
Contributor

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Attention The core contributors need to come back around and look at this ASAP. labels Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants