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

Cannot move tabs when Terminal is running as Administrator #12017

Closed
mfogliatto opened this issue Dec 22, 2021 · 3 comments
Closed

Cannot move tabs when Terminal is running as Administrator #12017

mfogliatto opened this issue Dec 22, 2021 · 3 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@mfogliatto
Copy link

Windows Terminal version

1.11.3471.0

Windows build number

10.0.22000.318

Other Software

No response

Steps to reproduce

  1. Run Terminal as Administrator
  2. Open a new tab so that the number of tabs opened is more than 1 (one)
  3. Attempt to move tabs around the tab area

Doing the aforementioned steps in a regular Terminal (i.e. non administator) works as expected.

Expected Behavior

Tabs should be moving around the tab area as desired (as shown in "Terminal - Non Admin.gif")

Terminal - Non Admin

Actual Behavior

Tabs just don't move (as shown in "Terminal - Admin.gif")

Terminal - Admin

@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 22, 2021
@237dmitry
Copy link

237dmitry commented Dec 22, 2021

The tab can be moved only using hotkeys (if configured) or from the "Command Palette"
Ctrl+Shift+P and moveTab forward/backward

I join your issue.

@zadjii-msft
Copy link
Member

This is by design. Please make sure to search for duplicates when filing new issues. This is something that we can't support right now due to some platform limitations. Turns out, even if we tried to support reordering tabs while elevated, the application would actually just crash 😨. See #4874, #5564 and others for more details.

/dup #6893

@ghost
Copy link

ghost commented Jan 3, 2022

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 3, 2022
@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 3, 2022
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