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.

Sign up for GitHub

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

Jump to bottom

Opacity resets after changing keyboard layout #12354

Closed
237dmitry opened this issue Feb 3, 2022 · 2 comments
Closed

Opacity resets after changing keyboard layout #12354

237dmitry opened this issue Feb 3, 2022 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@237dmitry
Copy link

Windows Terminal version

1.13.10336.0

Windows build number

10.0.22000.0

Other Software

No response

Steps to reproduce

  • Change opacity with Ctrl+Shift + wheel
  • Change keyboard layout ( default is Win+Space )

Expected Behavior

The opacity level should not change to the level specified in the opacity parameter.

Actual Behavior

The opacity is reset to the value specified in settings.json or up to the default value if it is not specified.
@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 Feb 3, 2022
@zadjii-msft
Copy link
Member

/dup #11522

@ghost
Copy link

ghost commented Feb 3, 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 closed this as completed Feb 3, 2022
@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 Feb 3, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zadjii-msft @237dmitry