Links/URLs get offset when certain unicode characters are printed

[Entrivax]

Environment

Windows build number: Windows 10 version 2004 (10.0.19041.0)
Windows Terminal version: Preview 1.5.3242.0

Steps to reproduce

Print certain unicode characters like this one: 𝓐

Expected behavior

Links/URLs should be valid.

Actual behavior

Links/URLs get offset and break with the presence of certain unicode characters.
For example, if the following text is printed:

𝓐𝓐𝓐
https://microsoft.com/

The hoverable link, clickable link and opened link is ps://microsoft.com/
If those unicode characters are not printed (if you scroll for example), the links work again.

2021-01-05_22-44-13_kWeoQrwJie.mp4

Note that the emoji doesn't cause the issue.
The code used in the video is:

console.log(`𝓐𝓐𝓐𝓐𝓐𝓐 123 https://microsoft.com/

✨ https://google.com/
https://google.fr/
https://youtube.com/
https://aka.ms/`)

[zadjii-msft]

Oh weird. I would have thought this was a dupe of #8121, but that one was fixed in 1.5.3142, so this must be it's own variation on the subject.

Those 𝓐 characters are really messing it up, huh.

[Entrivax]

It looks a lot like it, going the other way from the screen of that issue.

Those 𝓐 characters are really messing it up, huh.

Yeah, I found the problem when printing display usernames from an api. Not only the 𝓐 character, but also the rest of the alphabet written like that. Maybe there is more characters than that, I didn't try to find them all.

[skyline75489]

The 𝓐 is considered as two wide chars because of #8124. Another place we might want to use a comprehensive Unicode width estimator .

[zed76r]

[mas90]

Yeah, I found the problem when printing display usernames from an api. Not only the 𝓐 character, but also the rest of the alphabet written like that. Maybe there is more characters than that, I didn't try to find them all.

Definitely more characters than that, e.g. 🎟.

echo -e '\xf0\x9f\x8e\x9f http://www.example.com/' reproduces the bug on version 1.9.1445.0.

[DHowett]

Clever quick fix -- thanks @comzyh! I'm rolling this into the 1.11 and 1.12 servicing releases we're putting out to make Terminal more robust over the holidays. :)

[ghost]

🎉This issue was addressed in #11915, which has now been successfully released as Windows Terminal Preview v1.12.3472.0.:tada:

Handy links:

• Release Notes
• Store Download

[ghost]

🎉This issue was addressed in #11915, which has now been successfully released as Windows Terminal v1.11.3471.0.:tada:

Handy links:

• Release Notes
• Store Download

[CerebralDatabank]

I'm still having this issue with 5-digit Nerd Font Unicode characters on Windows 11…

[DHowett]

Which version of Terminal are you using? This issue was closed two years ago 🙂

[j4james]

@DHowett I think this regressed recently, because I was able to reproduce the issue until I got the update from 3 days ago. I'm assuming it was fixed by this:

Auto-detected URLs and search results are no longer pushed around by wide characters (oops) (#16787)

@CerebralDatabank Bottom line is you probably just need to get the very latest update.

[CerebralDatabank]

@DHowett Haha I knew that, but what can I say, I still have the issue 😅 thought replying here was better than opening a duplicate lol

@j4james I think you're right, latest stable is v1.19.10821.0 and I have v1.19.10573.0. But nothing happens when I check for updates in Terminal and there's no "Update" in the Store page.

If I install the latest release via the .msixbundle from here, will that mess up the existing link with MS Store updates? Or should I just wait until it rolls out to my device?

[DHowett]

thought replying here was better

you know what, that's totally fair! hah!

will that mess up the ... link

Nope, you can install the msixbundle from here and it will still hook up to the store for future updates!