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

Tabs are stuck scrolling even though there is room to show them all #3655

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

Comments

@JayAllison
Copy link

JayAllison commented Nov 21, 2019

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.476]
Windows Terminal version (if applicable): 0.6.2951.0


Any other software?

Steps to reproduce

I am using a Microsoft Surface Pro 7, along with a Surface dock and two external monitors. I expect that this issue is related to scaling (a common problem in my setup).

My Surface's display is set to 200% scaling, while my two external monitors are set to 100% scaling.

As I dock and undock, lock and unlock, throughout the day, Terminal can get into some funny visual states. Usually I can get everything working again by "restoring" (Windows + Down) and "maximizing" (Windows + Up), but today when I did that I cannot see all of my tabs without scrolling (see screenshot), even though there is plenty of space to display them.

Expected behavior

I would expect that all of the tabs are visible next to each other, since there is enough room to display them.

Actual behavior

I have 4 tabs open, but only one is showing; I have to scroll to see the rest of them.

image

I later found that if I close one of the tabs, all of the others will suddenly become visible. I didn't try adding a tab, but that might fix it, too?

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

Thanks for the report! This looks like a /dupe of #3300, with also some flavors of #3648 in it. I'll direct discussion to those threads.

@ghost
Copy link

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