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

Feature Request: Context Menu for Tabs #4276

Closed
tmknight opened this issue Jan 17, 2020 · 2 comments
Closed

Feature Request: Context Menu for Tabs #4276

tmknight opened this issue Jan 17, 2020 · 2 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

@tmknight
Copy link

Each Tab should have a Context Menu (e.g. Close, size)

Currently, tab title text can be longer than the tab width, requiring scroll-right to get to the close button.

This is in reference to #1912, however, #1912 has become muddled and inactive regarding the original topic of content menu.

@tmknight tmknight added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jan 17, 2020
@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 Jan 17, 2020
@zadjii-msft
Copy link
Member

I'm closing this as it's a exact /dupe of #1912. That's not an inactive issue, it's just on the backlog. When we're discussing larger features like that, it's helpful to have lots of requests in the thread, to help us understand the full scope of how the feature might be used, and lets us design the most flexible solution possible.

@ghost
Copy link

ghost commented Jan 17, 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 Jan 17, 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 Jan 17, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

No branches or pull requests

2 participants