Completion right after @bind$$-Parameter does not overwrite existing parameter

[Peter-Juhasz]

Version: VS 17.9.0 P2

Instead of overwriting, it keeps inserting the parameter name:

Rogzites.2023-12-22.091703.mp4

Similar to #9755, but not exactly the same. The underlying cause may be common (selecting the wrong completion span in text?), but it results in a different effect.

[alexgav]

@Peter-Juhasz thank you for the detailed video! Unfortunately I am unable to reproduce using a similar component. Would you be able to share a simple project that reproduces that issue for you? I am also unable to reproduce #9755 , so as you mentioned they might be related.

[Peter-Juhasz]

I can't share the project, but you can see the whole file in the recording.

It happens in multiple files and projects. Right now, I'm trying to reproduce it, but I don't even get any completions for a @bind-Property, which is either another symptom (sometimes happens this, sometimes happens that), another bug (which hides the one recorded in this issue), or it was accidentally "fixed" to a behavior which is not consistent with the C# experience (so that no completions are shown, but the caret doesn't move to the end of the completion span)?

[alexgav]

@Peter-Juhasz , thank you for your response. Am I understanding correctly that you are unable to reproduce duplicate text insertion anymore? I understand there may be other issues present, but want to focus on the duplicate text insertion (instead of text replacement) in this issue.

I did watch the video and I understand the issue was present in the past (it was also internally reported). However neither I nor other team members are able to reproduce it anymore, so I am assuming this particular issue is fixed (unless you can provide a project or page that still reproduces it). Please let me know!

We do appreciate the issues you report and the time you take to record the videos, it is very much appreciated and I want to make sure we are doing the due diligence here. However without being able to reproduce the issue, I cannot investigate this any further.

[Peter-Juhasz]

Sure, feel free to close it, it was not a high priority one and we can reopen it later if it comes up again. Thanks for the time anyway!

[alexgav]

Closing as I believe it was fixed by the VS platform changes (likely underling cause might have been non-alphanumeric character in the applicable-to span or completion text)