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

NOT DISPLAYING ALL OPENED TABS IN TAB LAYOUT. #3068

Closed
elecsomk10 opened this issue Oct 5, 2019 · 3 comments
Closed

NOT DISPLAYING ALL OPENED TABS IN TAB LAYOUT. #3068

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

Comments

@elecsomk10
Copy link

elecsomk10 commented Oct 5, 2019

Environment

Windows build number: Version 10.0.18362.356
Windows Terminal version: Version: 0.5.2762.0

Actual behavior:

Maximize window view : In maximize view of windows terminal, All tabs are displaying in tab layout.In this image I have opened 6 tabs in terminal.

terminal1

Minimize window view : But after minimizing the window view of windows terminal. Tab layout is not displaying all the 6 opened tabs. It is displaying only 3 tabs but actually 6 tabs are opened.It is hiding the remaining tabs which are not able to fit in tab layout.

terminal2

Same behavior getting for Maximize windows view also.

Expected behavior

For this issue we expect to accomplish the space of single tab layout by multiple tabs.

Example 1: Microsoft Edge browser
For multiple opened tabs Microsoft Edge browser provides 'scroll tab list forward' and 'scroll tab list backward' options to scroll over all the tabs and indicates the presence of multiple tabs.

terminal3

Example 2: Google Chrome browser
For multiple opened tabs Google Chrome browser squeeze all the opened tabs in single tab layout.

terminal4

Steps to reproduce

To resolve this issue we can add 'scroll tab list forward/backward' options or squeeze all the opened multiple tabs in tab layout.

@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 Oct 5, 2019
@j4james
Copy link
Collaborator

j4james commented Oct 5, 2019

The looks like a duplicate of #857 and/or #444.

@DHowett-MSFT
Copy link
Contributor

Yep! Thanks for the comprehensive write-up though. /dup #857 #444 and will be fixed by #1896 (in PR at #3027)

@ghost
Copy link

ghost commented Oct 6, 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 Oct 6, 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 Oct 6, 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