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

Bug Report - The maximize/restore button does not get updated when using a keyboard shortcut to maximize/restore the window. #2582

Closed
dam5s opened this issue Aug 28, 2019 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@dam5s
Copy link

dam5s commented Aug 28, 2019

Environment

Win32NT             10.0.18965.0 Microsoft Windows NT 10.0.18965.0                                                                                                                                                                                                                    
Windows Terminal (Preview)
Version: 0.4.2382.0

Steps to reproduce

When the window is not maximized, press Windows Key + Up to maximize it.
When the window is maximized, press Windows Key + Down to restore it.

Expected behavior

The maximize/restore button in the top right corner of the window changes icon to reflect the new state of the window.

Actual behavior

The button does not change.

@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 Aug 28, 2019
@zadjii-msft
Copy link
Member

This is a /dupe #1780

#1625 has miscellaneous other window management bugs tracked in it as well

@ghost
Copy link

ghost commented Aug 28, 2019

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 Aug 28, 2019
@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 Aug 28, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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