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

Incorrect Render After Terminal Is Full-Screened #4725

Closed
mmacoveiciuc opened this issue Feb 26, 2020 · 3 comments
Closed

Incorrect Render After Terminal Is Full-Screened #4725

mmacoveiciuc opened this issue Feb 26, 2020 · 3 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@mmacoveiciuc
Copy link

Environment

Windows build number: Microsoft Windows [Version 10.0.19569.1000]
Windows Terminal version: 0.9.433.0

Steps to reproduce

  1. Maximize the terminal (either by dragging the terminal to the top of the screen, or pressing the maximize icon on the top right of the application).
  2. Press the F11 hot-key to full-screen the application.
  3. Observe the top of the screen.

Expected behavior

The terminal is full-screened and only the main terminal pane is rendered.

Actual behavior

A white box is rendered on top of the terminal, presumably from the application navbar (taskbar?).

Full-Screen Render Incorrectly

@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 26, 2020
@mmacoveiciuc
Copy link
Author

Should have tested this sooner, sorry! This is only reproducible if you have the "Automatically hide the taskbar in desktop mode" set to enabled in Windows settings.

To access this setting:

  1. Right-click on your taskbar
  2. Click Taskbar Settings

@zadjii-msft
Copy link
Member

Thanks for the report! Your note that this only happens when "Automatically hide the taskbar in desktop mode" is actually very helpful, thanks!

This is already being tracked by another issue on our repo - please refer to #4224 for more discussion.

/dup #4224

@ghost
Copy link

ghost commented Feb 26, 2020

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 26, 2020
@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 26, 2020
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