SCM: Should use Ctrl-UpArrow instead of just UpArrow? #109275
Description
Issue Type: Bug
I've been using the scm commit history in insiders for the past few days. Here's some general feedback on the UX:
Unexpectedly navigating through history
I'll often hit up or down arrow to go to the next or previous line, and instead end up navigating through the history.
Could we require holding down ctrl or some other key to navigate history? I don't know why but I hit this a lot more in the commit history than I ever do in the search input boxes. Maybe this should be discussed at the UX sync?
Lost commit message
I've lost my commit messages a few times (possibly #109121). This is quite frustrating when you have written a long commit message, and it's something I think we need to fix this iteration
VS Code version: Code - Insiders 1.51.0-insider (7a3bdf4, 2020-10-23T07:32:22.213Z)
OS version: Darwin x64 19.6.0
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400) |
| GPU Status | 2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled metal: disabled_off multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on protected_video_decode: unavailable_off rasterization: enabled skia_renderer: disabled_off_ok video_decode: enabled webgl: enabled webgl2: enabled |
| Load (avg) | 2, 2, 2 |
| Memory (System) | 32.00GB (0.95GB free) |
| Process Argv | -psn_0_2732699 --crash-reporter-id cc7f0c9b-aa2b-4a45-8baa-81ffda32679e |
| Screen Reader | no |
| VM | 18% |