vscode: Insiders - can't select top menu at edge of screen due to padding pixel
Issue Type: Bug (or maybe new unwanted feature)
1 - try to select top menu with mouse at edge of screen
This still works fine in vanilla VSCode.
VS Code version: Code - Insiders 1.68.0-insider (c0769274fa136b45799edeccc0d0a2f645b75caf, 2022-05-23T05:17:12.256Z) OS version: Windows_NT x64 10.0.22621 Restricted Mode: No
System Info
| Item | Value |
|---|---|
| CPUs | Intel® Core™ i7-8809G CPU @ 3.10GHz (8 x 3096) |
| 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 oop_rasterization: enabled 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 |
| Load (avg) | undefined |
| Memory (System) | 15.92GB (5.93GB free) |
| Process Argv | C:\GitHub\space-03-astro_01 --crash-reporter-id aacb8121-be3d-4361-af2e-7d658f576ba7 |
| Screen Reader | no |
| VM | 0% |
Extensions (18)
| Extension | Author (truncated) | Version |
|---|---|---|
| astro | app | 0.1.148 |
| astro-vscode | ast | 0.19.0 |
| vscode-tailwindcss | bra | 0.8.4 |
| npm-intellisense | chr | 1.4.1 |
| vscode-markdownlint | Dav | 0.47.0 |
| dendron | den | 0.95.1 |
| dendron-markdown-shortcuts | den | 0.12.1 |
| dendron-paste-image | den | 1.1.0 |
| gitlens | eam | 12.0.6 |
| vscode-npm-script | eg2 | 0.3.25 |
| gitpod-desktop | git | 0.0.34 |
| customize-ui | ioc | 0.1.61 |
| monkey-patch | ioc | 0.1.16 |
| remote-ssh | ms- | 0.80.0 |
| remote-ssh-edit | ms- | 0.80.0 |
| vscode-yaml | red | 1.7.0 |
| svelte-vscode | sve | 105.16.1 |
| tailwind-snippets | Zar | 1.0.1 |
A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30422396
pythontb:30258533
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscod805:30301674
pythonvspyt200:30323110
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30404738
wslgetstarted:30449409
pythonvsnew555:30438690
vscscmwlcmt:30465136
cppdebug:30492333
vsclangdf:30492506
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 4
- Comments: 15 (12 by maintainers)
Commits related to this issue
- Use full titlebar height for menubar button hit area (Fix #150170) — committed to microsoft/vscode by daviddossett 2 years ago
- Use full titlebar height for menubar button hit area (Fix #150170) (#151250) * Use full titlebar height for menubar button hit area (Fix #150170) * Fix "more" toggle padding * fix focus outline... — committed to microsoft/vscode by daviddossett 2 years ago
- Fix #150170 — committed to microsoft/vscode by daviddossett 2 years ago
- Fix #150170 (#153348) — committed to microsoft/vscode by daviddossett 2 years ago
- Improve menu bar flyout positioning refs #150170 — committed to microsoft/vscode by sbatten 2 years ago
- fix menu bar flyout positioning (#153558) Improve menu bar flyout positioning refs #150170 — committed to microsoft/vscode by sbatten 2 years ago
The bug is released as 1.68.0, without any config to revert…
This is the intended behavior.
Here’s a roughly similar experience on GH. This is basically what I’ll be attempting to do:
Yeah I don’t consider it a bug, more an introduced stylistic choice which represents poor UX.
On Tue, 24 May 2022, 00:28 David Dossett, @.***> wrote: