vscode becomes "always on top" due to windows terminal

[seppeon]

Type: Bug

• Set "Windows Terminal" to be "Always On Top".
• Start debugging some terminal application (perhaps, or maybe open a terminal within vscode, I'm unused).

VS Code version: Code 1.74.3 (97dec172d3256f8ca4bfb2143f3f76b503ca0534, 2023-01-09T16:59:02.252Z) OS version: Windows_NT x64 10.0.19044 Modes: Sandboxed: No

System Info

|Item|Value| |---|---| |CPUs|AMD Ryzen 9 5950X 16-Core Processor (32 x 3400)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: disabled_off
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
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off| |Load (avg)|undefined| |Memory (System)|31.93GB (16.90GB free)| |Process Argv|| |Screen Reader|no| |VM|0%|

Extensions (27)

Extension|Author (truncated)|Version ---|---|--- asciidoctor-vscode|asc|2.9.8 markdown-mermaid|bie|1.17.3 doxdocgen|csc|1.4.0 docs-markdown|doc|0.2.117 gitlab-workflow|Git|3.57.3 latex-workshop|Jam|9.4.5 markdown-extended|jeb|1.1.3 cortex-debug|mar|1.6.10 cortex-debug-dp-stm32l4|mar|1.0.0 debug-tracker-vscode|mcu|0.0.13 memory-view|mcu|0.0.18 rtos-views|mcu|0.0.3 python|ms-|2022.20.2 jupyter|ms-|2022.11.1003412109 jupyter-keymap|ms-|1.0.0 jupyter-renderers|ms-|1.0.13 vscode-jupyter-cell-tags|ms-|0.1.6 vscode-jupyter-slideshow|ms-|0.1.5 remote-wsl|ms-|0.72.0 cmake-tools|ms-|1.12.27 cpptools|ms-|1.14.0 hexeditor|ms-|1.9.9 test-adapter-converter|ms-|0.1.6 vscode-markdown-notebook|ms-|0.0.26 command-variable|rio|1.47.0 graphviz-interactive-preview|tin|0.3.5 cmake|twx|0.0.17 (1 theme extensions excluded)

[deepak1556]

/gifPlease

[VSCodeTriageBot]

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.

If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.

Happy coding!

[seppeon]

Hmm. I must have written this tired... I'm not quite sure what I was trying to say. I'd say close the issue and I'll reopen with a more clear explanation if it reoccurs.