Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dragging text upwards triggers scrolling far too early #218248

Open
proimage opened this issue Jun 26, 2024 · 0 comments
Open

Dragging text upwards triggers scrolling far too early #218248

proimage opened this issue Jun 26, 2024 · 0 comments
Assignees

Comments

@proimage
Copy link

proimage commented Jun 26, 2024

Type: Bug

  1. Create a document with multiple screens of text (one way is to set to HTML, then use Emmet to auto-complete lorem*60 or so).
  2. Scroll down to the middle-ish, so there's plenty to vertically scroll in either direction.
  3. Select a bit of text.
  4. Click and hold in the selection to drag that text downwards, and once you get near the bottom edge (90-95% of the way there?), the document should scroll a few lines each time there's mouse movement. This is the normal, expected behavior.
  5. Now drag upwards. Instead of scrolling being triggered near the top edge, it gets triggered at around the vertical halfway point. This is the bug.

VS Code version: Code 1.90.2 (5437499, 2024-06-18T22:34:26.404Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info
Item Value
CPUs Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz (6 x 3696)
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
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
Load (avg) undefined
Memory (System) 31.94GB (10.01GB free)
Process Argv --disable-extensions --crash-reporter-id cf829538-9b7f-4bbd-892b-dfe6bf5e9a2a
Screen Reader no
VM 0%
Extensions disabled
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
vscaac:30438847
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonnoceb:30805159
asynctok:30898717
pythonregdiag2:30936856
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
jchc7451:31067544
chatpanelc:31048052
dsvsc021:30996838
bdiig495:31013172
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
dwnewjupytercf:31046870
2f103344:31071589
legacy_priority:31082724

Video of the issue:

Screen.Recording.2024-06-26.090325.mp4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants