Pressing "Shift" opens Edge Settings on a new target, inactivating the current target. Headless Mode Only.

microsoft / vscode-edge-devtools

A VSCode extension that allows you to use browser devtools from within the editor. The devtools will connect to an instance of Microsoft Edge giving you the ability to alter CSS styling, perform diagnostics, and debugging. Get it now at http://aka.ms/devtools-for-code

https://docs.microsoft.com/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension

MIT License

745 stars 254 forks source link

Pressing "Shift" opens Edge Settings on a new target, inactivating the current target. Headless Mode Only. #2386

Open arbonaa opened 2 weeks ago

arbonaa commented 2 weeks ago

Environment (please complete the following information):

OS (e.g., Windows 10): MacOS Version 14.6.1 (23G93)
Extension version (e.g., 1.2.3): 2.1.5

Describe the bug:

When working on a tab, if you press "Shift" it inactivated the current tab and opens a new one in Edge Settings. This makes the extension unusable.

Repro steps:

Launch new instance.
Navigate to any site. (ex. www.google.com)
Press "Shift"
Instance deactivates and new instance opens in Edge Settings

Expected behavior:

Pressing "Shift" does nothing.

Additional context:

Checked all the vscode keybinds, nothing there seems to cause the issue. This only happens in headless mode.

AB#53620264

captainbrosset commented 2 weeks ago

Pressing Shift doesn't do anything for me, so I have not been able to reproduce this yet. Would it be feasible for you to record a short screencast showing the issue in action? Or maybe posting a few screenshots, showing the before/after states? I would like to make sure I understand the problem you are seeing.

arbonaa commented 2 weeks ago

here is a quick screen capture of the issue,

https://github.com/user-attachments/assets/88ef000b-0768-41c1-af50-8aae131c4e58

captainbrosset commented 1 week ago

Thanks a lot for this. I tried to reproduce this locally, but couldn't. I tried on a Windows PC, so that might explain the difference. I'll mark this as a bug for the team to investigate. In the meantime, maybe try to see if you don't have the Shift key mapped to some action, either in macOS, or in Edge, or VSCode. I don't know if/how this is possible, but that could explain it.