Issue Type: Bug
When closing files with unsaved changes, a dialog open with the three possible actions: "Don't save", "Cancel", "Save" in that order.
When closing an unsaved workspace, a similar dialog appear with actions "Save", "Cancel", "Don't save" in that order.
That feel inconsistent and could cause confusion. The order should probably be the same in every dialog.
VS Code version: Code 1.42.0 (ae08d54, 2020-02-06T10:51:23.649Z)
OS version: Linux x64 5.0.0-38-generic
System Info
| Item |
Value |
| CPUs |
Intel(R) Core(TM) i5-7260U CPU @ 2.20GHz (4 x 3340) |
| 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: disabled_off
protected_video_decode: unavailable_off
rasterization: disabled_software
skia_renderer: disabled_off
surface_control: disabled_off
surface_synchronization: enabled_on
video_decode: unavailable_off
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off
webgl: enabled
webgl2: enabled |
| Load (avg) |
1, 1, 1 |
| Memory (System) |
11.62GB (0.87GB free) |
| Process Argv |
remarques.md --no-sandbox |
| Screen Reader |
no |
| VM |
0% |
Extensions (14)
| Extension |
Author (truncated) |
Version |
| npm-intellisense |
chr |
1.3.0 |
| path-intellisense |
chr |
1.4.2 |
| vscode-eslint |
dba |
2.0.15 |
| vscode-npm-script |
eg2 |
0.3.11 |
| search-node-modules |
jas |
1.3.0 |
| vscode-exec-node |
mir |
0.5.1 |
| vscode-language-pack-fr |
MS- |
1.42.2 |
| cpptools |
ms- |
0.26.3 |
| debugger-for-chrome |
msj |
4.12.6 |
| vscode-npm-scripts |
tra |
0.2.1 |
| vim |
vsc |
1.12.4 |
| nodejs-extension-pack |
wad |
0.1.9 |
| vscode-todo-highlight |
way |
1.0.4 |
| JavaScriptSnippets |
xab |
1.7.2 |
Issue Type: Bug
When closing files with unsaved changes, a dialog open with the three possible actions: "Don't save", "Cancel", "Save" in that order.
When closing an unsaved workspace, a similar dialog appear with actions "Save", "Cancel", "Don't save" in that order.
That feel inconsistent and could cause confusion. The order should probably be the same in every dialog.
VS Code version: Code 1.42.0 (ae08d54, 2020-02-06T10:51:23.649Z)
OS version: Linux x64 5.0.0-38-generic
System Info
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: disabled_software
skia_renderer: disabled_off
surface_control: disabled_off
surface_synchronization: enabled_on
video_decode: unavailable_off
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off
webgl: enabled
webgl2: enabled
Extensions (14)