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.

Sign up for GitHub

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

Jump to bottom

Specify tab header width in profiles.json #3792

Closed
maciejpankanin opened this issue Dec 1, 2019 · 3 comments
Closed

Specify tab header width in profiles.json #3792

maciejpankanin opened this issue Dec 1, 2019 · 3 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@maciejpankanin
Copy link

Description of the new feature/enhancement

The ability to set something like minimal tab width or to set all tabs to have same width.

Adnotacja 2019-12-01 094904
@maciejpankanin maciejpankanin added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Dec 1, 2019
@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 Dec 1, 2019
@jj10133
Copy link

jj10133 commented Dec 2, 2019 •
edited
Loading

I would like to suggest that let's make the tab header width the maximum tabrow that covers till. As we add tabs we divide the total distance by the number of tabs into equal portions. Plus we should have a limit on the minimum size of tab

@DHowett-MSFT
Copy link
Contributor

This is a /dupe of #597. Thanks!

@ghost
Copy link

ghost commented Dec 2, 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 Dec 2, 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 Dec 2, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@DHowett-MSFT @maciejpankanin @jj10133