You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can you share more details? As is, there is not enough information here for us to investigate further.
We're not aware of any issues in this area so any further information would be helpful in allowing us to reproduce this issue.
Am consistently experiencing this issue for couple of days. Basically it makes read-write sessions unusable.
The manifestation of it is following - when I host read-write session on macOS and Windows client joins I'm unable to successfully persist changes into a file that was created by Windows client during LiveShare. If I type characters, they do appear at macOS side, but observing the Windows client's screen (e.g., via Teams screen share) confirms that edits don't show up/are not successfully transferred by LiveShare to Windows side. In several cases, doing these futile saves even led to a mish-mash situation/garbled up files between clients (fused several lines into single and other weirdness).
Curiously, there are no observed issues with same Windows client's edits in their appearance/correctness on macOS. That is, I can properly see in realtime the Windows client's activity/edits on a macOS VS Code.
Type: Bug
Seems like cursor position is tracked incorrectly likely due to env. new line differences between platforms
Extension version: 1.0.5918
VS Code version: Code 1.86.2 (Universal) (903b1e9d8990623e3d7da1df3d33db3e42d80eda, 2024-02-13T19:42:13.651Z)
OS version: Darwin arm64 23.0.0
Modes:
System Info
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
webgl: enabled
webgl2: enabled
webgpu: enabled
A/B Experiments
The text was updated successfully, but these errors were encountered: