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
Live Share extension currently uses the decoration API to render a name tag near the cursor
It works fine when the decoration is in the middle of the viewport (also when there are more than one line in the editor). When it's at the first line and top set to -1rem, the decoration will be cut off as the ViewLines/ScrollableElement has overflow: hidden.
LS work arounds this issue by rendering the name tag under the line when the cursor is on the first line. While this doesn't work for notebook as often the cell input only has one line (you can also reproduce this issue with Text Editor)
I'm wondering what's the best way to mitigate this issue, maybe some floating (overflowing) decorations? It sounds crazy so I'd like to know @alexdima 's suggestion on this.
The text was updated successfully, but these errors were encountered:
The name appears to almost fit in the last screenshot.
Is it possible to do something pragmatic and just add padding to the editor when there is a live share session going on? (The editor option is literally called padding)
Live Share extension currently uses the decoration API to render a name tag near the cursor
It works fine when the decoration is in the middle of the viewport (also when there are more than one line in the editor). When it's at the first line and top set to
-1rem
, the decoration will be cut off as the ViewLines/ScrollableElement hasoverflow: hidden
.LS work arounds this issue by rendering the name tag under the line when the cursor is on the first line. While this doesn't work for notebook as often the cell input only has one line (you can also reproduce this issue with Text Editor)
I'm wondering what's the best way to mitigate this issue, maybe some floating (overflowing) decorations? It sounds crazy so I'd like to know @alexdima 's suggestion on this.
The text was updated successfully, but these errors were encountered: