Unable to open new tabs or select other options on 0.7.3451.0 #5669

Closed
opened 2026-01-31 00:18:54 +00:00 by claunia · 5 comments
Owner

Originally created by @Sparker0i on GitHub (Dec 22, 2019).

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Windows 10 18363 x64
Windows Terminal version (if applicable): 0.7.3451.0

Any other software? Maybe Powertoys but I don't see why that should affect

Steps to reproduce

  1. Open Windows Terminal
  2. Try opening a new tab

Expected behavior

New tab should open

Actual behavior

New tab wont open. There's no hover effect around the + button, or even the drop down button. We can't even minimize, maximise or close using the buttons on the tab bar. None of them get highlighted on hover.
Keyboard shortcuts work however..

Originally created by @Sparker0i on GitHub (Dec 22, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Windows 10 18363 x64 Windows Terminal version (if applicable): 0.7.3451.0 Any other software? Maybe Powertoys but I don't see why that should affect ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> 1. Open Windows Terminal 2. Try opening a new tab # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> New tab should open # Actual behavior <!-- What's actually happening? --> New tab wont open. There's no hover effect around the + button, or even the drop down button. We can't even minimize, maximise or close using the buttons on the tab bar. None of them get highlighted on hover. Keyboard shortcuts work however..
Author
Owner

@mkitzan commented on GitHub (Dec 27, 2019):

Doesn't repro for me. Could you post some screen caps or something a little more to go on? Sounds like it's related to the TabView ui xaml element though.

@mkitzan commented on GitHub (Dec 27, 2019): Doesn't repro for me. Could you post some screen caps or something a little more to go on? Sounds like it's related to the `TabView` ui xaml element though.
Author
Owner

@zadjii-msft commented on GitHub (Dec 30, 2019):

@Sparker0i Could you just quick test if uninstalling powertoys fixes this? WE do some real weird stuff with our window frame, and I'd be curious to know if Powertoys doesn't play nice with that.

If not, we're probably going to need an in-house repro to be able to investigate this further unfortunately.

Does resizing the window fix these buttons? This is totally spitballing - I really don't know how this might happen.


EDIT: After getting through more of my inbox, https://github.com/microsoft/terminal/issues/3325#issuecomment-569546479 seems to also suggest that powertoys doesn't play nicely with WT.

@zadjii-msft commented on GitHub (Dec 30, 2019): @Sparker0i Could you just quick test if uninstalling powertoys fixes this? WE do some real weird stuff with our window frame, and I'd be curious to know if Powertoys doesn't play nice with that. If not, we're probably going to need an in-house repro to be able to investigate this further unfortunately. Does resizing the window fix these buttons? This is totally spitballing - I really don't know how this might happen. <hr> EDIT: After getting through more of my inbox, https://github.com/microsoft/terminal/issues/3325#issuecomment-569546479 seems to also suggest that powertoys doesn't play nicely with WT.
Author
Owner

@Sparker0i commented on GitHub (Dec 31, 2019):

Yes, uninstalling Powertoys latest fixed this. I am not sure why but earlier versions of Terminal used to work well with Powertoys

Cant even resize the windows with Powertoys

@Sparker0i commented on GitHub (Dec 31, 2019): Yes, uninstalling Powertoys latest fixed this. I am not sure why but earlier versions of Terminal used to work well with Powertoys Cant even resize the windows with Powertoys
Author
Owner

@DHowett-MSFT commented on GitHub (Jan 6, 2020):

This looks like a /dupe of #3325.

@DHowett-MSFT commented on GitHub (Jan 6, 2020): This looks like a /dupe of #3325.
Author
Owner

@ghost commented on GitHub (Jan 6, 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 commented on GitHub (Jan 6, 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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#5669