microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
162.15k stars 28.53k forks source link

Menu bar and contextual tools unavailable when going full screen with highlighted code #164852

Closed BenjaminFox1 closed 1 year ago

BenjaminFox1 commented 1 year ago

Type: Bug

Going full screen with any code highlighted causes menu items to be unavailable.

VS Code version: Code 1.72.2 (d045a5eda657f4d7b676dedbfa7aab8207f8a075, 2022-10-12T22:16:26.920Z) OS version: Linux x64 5.15.0-52-generic Modes: Sandboxed: No

System Info |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-4578U CPU @ 3.00GHz (4 x 3395)| |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: disabled_software
video_encode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off| |Load (avg)|1, 1, 1| |Memory (System)|15.51GB (10.76GB free)| |Process Argv|--unity-launch --crash-reporter-id ee3d0e5f-0c3c-460c-903e-14629df12b5e| |Screen Reader|no| |VM|0%| |DESKTOP_SESSION|ubuntu| |XDG_CURRENT_DESKTOP|Unity| |XDG_SESSION_DESKTOP|ubuntu| |XDG_SESSION_TYPE|wayland|
Extensions (22) Extension|Author (truncated)|Version ---|---|--- prettier-vscode|esb|9.9.0 vscode-firefox-debug|fir|2.9.8 better-cpp-syntax|jef|1.16.3 web-accessibility|Max|0.2.83 vscode-dotnet-runtime|ms-|1.5.0 python|ms-|2022.16.1 vscode-pylance|ms-|2022.10.40 jupyter|ms-|2022.9.1202862440 jupyter-keymap|ms-|1.0.0 jupyter-renderers|ms-|1.0.10 vscode-jupyter-cell-tags|ms-|0.1.6 vscode-jupyter-slideshow|ms-|0.1.5 cpptools|ms-|1.12.4 cpptools-extension-pack|ms-|1.3.0 material-icon-theme|PKi|4.21.0 LiveServer|rit|5.7.9 synthwave-vscode|Rob|0.1.14 p5-vscode|sam|1.2.11 html5-boilerplate|sid|1.1.1 vscode-stylelint|sty|1.2.3 vscode-todo-highlight|way|1.0.5 html-css-class-completion|Zig|1.20.0 (1 theme extensions excluded)
gjsjohnmurray commented 1 year ago

I'm not seeing any difference in full screen mode depending on whether or not I have code highlighted.

Are you referring to the menu bar not displaying when in full screen mode (F11 on my Windows workstation)? If so, did you know that pressing the Alt key (on Windows at least) reveals it?

/gifPlease

VSCodeTriageBot commented 1 year ago

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).

Happy coding!

BenjaminFox1 commented 1 year ago

Hi John, thanks for the response, it turns out that because I am enabling 'Mouse keys' in the Ubuntu accessibility options this causes vscode to have the issue. Disabling seemed to resolve the issue.

I'm not sure whether this is also an issue for other operating systems. Ben

On Fri, Oct 28, 2022 at 9:53 AM John Murray @.***> wrote:

I'm not seeing any difference in full screen mode depending on whether or not I have code highlighted.

Are you referring to the menu bar not displaying when in full screen mode (F11 on my Windows workstation)? If so, did you know that pressing the Alt key (on Windows at least) reveals it?

/gifPlease

— Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode/issues/164852#issuecomment-1294628305, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATV73HEHGVHI2DKBFECRAWDWFOA7TANCNFSM6AAAAAARQXPE4Y . You are receiving this because you authored the thread.Message ID: @.***>

sbatten commented 1 year ago

@BenjaminFox1 I'm not having an Ubuntu box to test this at the moment, can you provide a screen recording to explain the issue further?

BenjaminFox1 commented 1 year ago

I've tried producing a screen recording that produces the same problem, but for some reason it seems to work okay when I'm trying to record. It maybe something to do with the mouse keys accessibility option losing focus when it is in full screen. Sorry, I can be of no further assistance right now. kind regards Ben

On Fri, Oct 28, 2022 at 6:58 PM SteVen Batten @.***> wrote:

@BenjaminFox1 https://github.com/BenjaminFox1 I'm not having an Ubuntu box to test this at the moment, can you provide a screen recording to explain the issue further?

— Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode/issues/164852#issuecomment-1295235850, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATV73HAIKBYYR7H55EDRH6DWFQAZVANCNFSM6AAAAAARQXPE4Y . You are receiving this because you were mentioned.Message ID: @.***>

rzhao271 commented 1 year ago

I have an Ubuntu VM now, but I'm wondering what you mean by menu items? Can you send a screenshot?

BenjaminFox1 commented 1 year ago

Sure, here you go. I'm having trouble replicating the issue when using any recording device.

Essentially, if you have mouse keys selected as an option, go full screen, highlight code, then right-click or select menu options, they don't appear.

Hope this helps on the path. regards Ben

On Sat, Oct 29, 2022 at 12:42 AM Raymond Zhao @.***> wrote:

I have an Ubuntu VM now, but I'm wondering what you mean by menu items? Can you send a screenshot?

— Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode/issues/164852#issuecomment-1295583769, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATV73HGQDPGOT2Y5DFK3MZDWFRJGRANCNFSM6AAAAAARQXPE4Y . You are receiving this because you were mentioned.Message ID: @.***>

VSCodeTriageBot commented 1 year ago

Hey @deepak1556 @sbatten @rzhao271, this issue might need further attention.

@BenjaminFox1, you can help us out by closing this issue if the problem no longer exists, or adding more information.

BenjaminFox1 commented 1 year ago

I no longer have the issue