Issue Type: Bug
With todays update, the cursor doesn't change to the selection mode when is over a layout boundary so I can't resize my editor layouts.
There is any new way to do that? or it is only a bug?
VS Code version: Code - Insiders 1.46.0-insider (d0a3feff23c47876412f5e289b935aabf02c71ae, 2020-05-13T05:35:51.092Z)
OS version: Windows_NT x64 10.0.18363
System Info
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (8 x 3411)|
|GPU Status|2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: enabled
webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|15.98GB (9.69GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
Extensions (3)
Extension|Author (truncated)|Version
---|---|---
python|ms-|2020.5.78807
remote-wsl|ms-|0.44.2
material-icon-theme|PKi|4.1.0
(1 theme extensions excluded)
It seems that this is related to this PR: https://github.com/microsoft/vscode/pull/97266
The sashes are still present, but their position and behaviour is incorrect:

I guess it would be better to draw @lszomoru @joaomoreno attention to this ticket.
is there any way for me to downgrade this version until the bug will be fixed? I can only find "check for updates" in the preferences... Thank you for your help, @YBogomolov
I've unreleased that build and will be releasing a new Insiders today with the fix. Sorry for the disturbance.
Fix is in: https://github.com/microsoft/vscode/commit/e88b8d32aa7233f6cb3665f6dae9fa78b1e8aafb
Build running, it should be out in about 1h 馃挭
Meanwhile, if you check for updates once again, you should be reverted back to a good build, until the fix finishes building.
Meanwhile, if you check for updates once again, you should be reverted back to a good build, until the fix finishes building.
It works perfect! Thank you very much @joaomoreno 馃殌
Thank you for being on top of things! 馃檹
We have published a new Insiders build that contains the fix for this issue. Apologies for the inconvenience.
Thank you for solving it so quick! you are 馃殌 's!
Most helpful comment
I've unreleased that build and will be releasing a new Insiders today with the fix. Sorry for the disturbance.