Auto closing tags not working

[Feuerhamster]

Describe what happened: There are two of us in a LiveShare session in VS Code editing an HTML file. If the participant is not in the file, the HTML auto closing tags do not work. If she is in the file, the auto close works, but her cursor jumps there. It looks like the auto closing was done from her side in that case.

In a new VS Code window without LiveShare the HTML auto closing tags works fine.

What was your system configuration? Product and Version: VS Code 1.62.3 OS Version: Windows 10 2004 (Build 19041.1288) Live Share Extension Version: v1.0.5090 Target Platform or Language: HTML

Steps to Reproduce / Scenario:

1. Open a LiveShare session in VS Code
2. Invite a participant
3. Make a new HTML file, but the participant should not open this file yet
4. Try to write HTML tags and pay attention if the tags are auto closing
5. Now the participant should open the file
6. Now try again writing HTML tags
7. The auto closing should work now, but the cursor of the participant jumps there

Please attach logs to this issue: livesharelogs.zip

Video: https://youtu.be/Va8_FqQvYJI

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically in 2 days.

[Feuerhamster]

The problem is still there

[Fasteroid]

Would love a fix for this sometime soon.

[pmiossec]

Still present in last version of VSCode (1.82.2) and it is very annoying to say so....

Another way to reproduce:

1. Open an html file with content
2. Open a LiveShare session in VS Code & Invite a participant
3. Host put the cursor at a specific place (top of file is good to see the behavior)
4. Participant use completion to enter a <div></div> (i.e. type div then use emmet completion). It seems that some tag fail and some not (div, article, p, i are failing but some other not...)
5. Result: host cursor jumped (best case) and sometimes some bad content is added like </body> also (worst case!)

See the case:

I reproduce it easily with the host and participant on the same computer so it doesn't seem to be due to network latency. I reproduce it also with a profile with all extensions disabled, except "Live share" so it doesn't seem to be due to another extension.

PS: I'm really surprised that no one from VSCode team reproduce it because it happens really often when editing html files in pair programming. I was not able to reproduce it using completion in tsx files.

[pmiossec]

A little more information: the content added is the one of the parent. See this other case:

So it seems it tries to close the current tag and the parent one...

[derekbekoe]

We’re not able to prioritize this issue over the other higher-impact issues we receive every week, based on the votes and comments from others in the community and our understanding of the issue. We understand this may be disappointing; we've all been there, whether in this project or others we've contributed to. However, rest assured that we love your input. If you feel it deserves to stay open, then clarify your use case and contact us to let us know how severe it’s for you.