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

Cannot have maximum opacity by default if acrylic is enabled #13986

Closed
ofek opened this issue Sep 14, 2022 · 2 comments
Closed

Cannot have maximum opacity by default if acrylic is enabled #13986

ofek opened this issue Sep 14, 2022 · 2 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

@ofek
Copy link
Contributor

ofek commented Sep 14, 2022

Windows Terminal version

1.16.252

Windows build number

10.0.19044.0

Other Software

No response

Steps to reproduce

This has been bugged but I thought this release might've fixed it

    "profiles":
    {
        "defaults": {
            "opacity": 100,
            "useAcrylic": true,
  1. Open a window with colors
  2. Open Terminal
  3. Observe bleed-through
  4. Hold down key binding that increases opacity
  5. Notice nothing
  6. Press key binding that decreases opacity once
  7. Press key binding that increases opacity once
  8. Notice actual maximum opacity

Expected Behavior

Maximum opacity by default

Actual Behavior

Near-maximum opacity by default

@ofek ofek added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Sep 14, 2022
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Sep 14, 2022
@zadjii-msft
Copy link
Member

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #12880 for more discussion.

/dup #12880

@ghost
Copy link

ghost commented Sep 14, 2022

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!

@ghost ghost 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-Tag-Fix Doesn't match tag requirements labels Sep 14, 2022
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

2 participants