Skip to content

F11 (step into) when debugging sometimes triggers the Full Screen command #78251

@eamodio

Description

@eamodio

Issue Type: Bug

I've only noticed this fairly recently, but when debugging sometimes pressing F11 results in the full screen command rather than step into.

It seems like this was also noted here: #70932 (comment)

/cc @isidorn

VS Code version: Code - Insiders 1.37.0-insider (d5900c6, 2019-07-31T05:24:41.973Z)
OS version: Windows_NT x64 10.0.18362

System Info
Item Value
CPUs Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (8 x 4008)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_deferred_display_list: disabled_off
skia_renderer: disabled_off
surface_synchronization: enabled_on
video_decode: enabled
viz_display_compositor: disabled_off
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 31.93GB (17.41GB free)
Process Argv
Screen Reader no
VM 0%

Metadata

Metadata

Assignees

Labels

bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions