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

Title bar icons unusable #3755

Closed
mKay00 opened this issue Nov 27, 2019 · 5 comments
Closed

Title bar icons unusable #3755

mKay00 opened this issue Nov 27, 2019 · 5 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@mKay00
Copy link
Contributor

mKay00 commented Nov 27, 2019

Environment

Windows build number: 10.0.18363.0 and 10.0.19033.0
Windows Terminal version (if applicable): 0.7.3291.0

Steps to reproduce

I don't know, I just started Windows Terminal today on my PC and it happened. A few hours later the same happened on my Surface Pro 5

Expected behavior

I expect the title bar to be clickable and functioning (e.g. clicking on the "+" opens a new tab or clicking the arrow opens the option pane)

Actual behavior

The whole title bar is unclickable. Including the "X" to close the tab, the "+" to open a new tab, the arrow for the options pane, as well as minimize, maximize and close. But I can use the open terminal window and enter commands. And I can move the window when clicking on the title bar and dragging.

Weirdly enough it works (for now) on my PC, without doing anything.

Edit: Something I just noticed is that the mouse cursor seems to keep the symbol when entering the Windows Terminal window, i.e. if I move my mouse slowly from left to right into the Terminal window, the cursor changes to the horizontal resize symbol and keeps this symbol as long as I am inside the Terminal window with my mouse (except between the part between the down arrow for the options pane and the minimize button, there the mouse cursor changes to the normal mouse pointer)

@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 Nov 27, 2019
@1kjo
Copy link
Contributor

1kjo commented Nov 27, 2019

Sounds similar to #3325.

@mKay00
Copy link
Contributor Author

mKay00 commented Nov 27, 2019

Indeed! I looked for similar issues, but couldn't find one. So I guess this can be closed. But the issue apparently still exists 😅

@1kjo
Copy link
Contributor

1kjo commented Nov 28, 2019

Yeah it's hard to look for duplicate issues if you don't have the right keywords.

@DHowett-MSFT
Copy link
Contributor

Thanks for the report @mKay00 and finding the dupe @greg904! /dup #3325.

@ghost
Copy link

ghost commented Nov 30, 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 Nov 30, 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 Nov 30, 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

3 participants