Extension Blocks the work on VSCode

[sfedchyk64]

Type: Bug

I’m unable to use VSCode effectively because essential functionalities like the search feature (Ctrl+Shift+F) and file browsing (Ctrl+P) are not working as expected.

Extension version: 3.5.157 VS Code version: Code 1.83.1 (f1b07bd25dfad64b0167beb15359ae573aecd2cc, 2023-10-10T23:48:05.904Z) OS version: Windows_NT x64 10.0.22631 Modes:

System Info

|Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (12 x 2592)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled| |Load (avg)|undefined| |Memory (System)|15.79GB (3.10GB free)| |Process Argv|--crash-reporter-id 6c6b286b-d1f5-445f-a5db-57d7273b832d| |Screen Reader|no| |VM|0%|

A/B Experiments

``` vsliv368cf:30146710 vspor879:30202332 vspor708:30202333 vspor363:30204092 pythonvspyt551:31179978 vscod805:30301674 binariesv615:30325510 vsaa593:30376534 py29gd2263:31024239 c4g48928:30535728 azure-dev_surveyone:30548225 a9j8j154:30646983 962ge761:30959799 pythonnoceb:30805159 asynctok:30898717 pythonmypyd1:30879173 pythontbext0:30879054 cppperfnew:31000557 dsvsc020:30976470 pythonait:31006305 dsvsc021:30996838 jg8ic977:31013176 dvdeprecation:31068756 dwnewjupytercf:31046870 nativerepl2:31139839 pythonrstrctxt:31112756 iacca1:31171482 notype1:31157159 5fd0e150:31155592 dwcopilot:31170013 stablechunks:31184530 ```

[PilarHidalgo]

Hi @sfedchyk64 , Due to the extension blocking shortcuts, you need to click or switch to another tab in VSCode outside of the extension to use them. This will allow you to access the commands you mentioned.

[Adel242]

Hi @sfedchyk64.

The functionalities or shortcut commands specific to the extension work properly. However, when you click within the extension, they get deactivated because they might cause potential conflicts with the extension's own commands. If you click in Visual Studio (outside of the extension), the commands should work without any issues.

Best regards,