URL highlight issues with emoji #15944

Closed
opened 2026-01-31 04:52:59 +00:00 by claunia · 5 comments
Owner

Originally created by @ggnkua on GitHub (Nov 21, 2021).

Windows Terminal version

1.11.2921.0

Windows build number

10.0.19043.1348

Other Software

WSL 2 (using Ubuntu 20.04.2 LTS)

Steps to reproduce

Open a wsl2 and paste the following line:

😃👍🕹🕹️ http://microsoft.com

In my machine I get:

image

Notice the two spaces between // and microsoft.com. Sometimes those two spaces appear, some times they don't.

If I move the cursor and delete the two spaces, and then try to highlight the URL I get:

image

Trying to ctrl-click the URL gives:

image

Expected Behavior

The URL should appear without spaces, the URL should be underlined and clickable.

Actual Behavior

The URL failed to highlight properly, and when ctrl-clicking it, it produced the error shown in the last screenshot in "steps to reproduce"

Originally created by @ggnkua on GitHub (Nov 21, 2021). ### Windows Terminal version 1.11.2921.0 ### Windows build number 10.0.19043.1348 ### Other Software WSL 2 (using Ubuntu 20.04.2 LTS) ### Steps to reproduce Open a wsl2 and paste the following line: 😃👍🕹🕹️ http://microsoft.com In my machine I get: ![image](https://user-images.githubusercontent.com/5121492/142774913-f8035fcf-9d31-48d0-9169-6b6b12e2f0a0.png) Notice the two spaces between `//` and `microsoft.com`. Sometimes those two spaces appear, some times they don't. If I move the cursor and delete the two spaces, and then try to highlight the URL I get: ![image](https://user-images.githubusercontent.com/5121492/142774996-8cc140a4-1008-4c64-a0b8-100a00cf603f.png) Trying to ctrl-click the URL gives: ![image](https://user-images.githubusercontent.com/5121492/142775025-83bd973b-1e79-41f6-a54c-465235df9cd9.png) ### Expected Behavior The URL should appear without spaces, the URL should be underlined and clickable. ### Actual Behavior The URL failed to highlight properly, and when ctrl-clicking it, it produced the error shown in the last screenshot in "steps to reproduce"
claunia added the Resolution-Duplicate label 2026-01-31 04:52:59 +00:00
Author
Owner

@j4james commented on GitHub (Nov 21, 2021):

This could probably be considered a duplicate of #8709. More fundamentally, though, I think the issue is that we can't handle characters outside the BMP which have a narrow width. I expect this will be solved by #8000.

@j4james commented on GitHub (Nov 21, 2021): This could probably be considered a duplicate of #8709. More fundamentally, though, I think the issue is that we can't handle characters outside the BMP which have a narrow width. I expect this will be solved by #8000.
Author
Owner

@ggnkua commented on GitHub (Nov 21, 2021):

Oh gosh, so it has been reported already. I tried searching for an open issue but I wasn't sure how to search for it.

Should we close this as duplicate or leave open?

@ggnkua commented on GitHub (Nov 21, 2021): Oh gosh, so it has been reported already. I tried searching for an open issue but I wasn't sure how to search for it. Should we close this as duplicate or leave open?
Author
Owner

@j4james commented on GitHub (Nov 21, 2021):

Not to worry. Even if closed as a duplicate, it's good to have easily reproducible test cases like this to check whether a future fix is actually working as expected. One of the core devs will probably close this if they confirm it's definitely a dup.

@j4james commented on GitHub (Nov 21, 2021): Not to worry. Even if closed as a duplicate, it's good to have easily reproducible test cases like this to check whether a future fix is actually working as expected. One of the core devs will probably close this if they confirm it's definitely a dup.
Author
Owner

@zadjii-msft commented on GitHub (Nov 22, 2021):

No worries, this definitely looks like /dup #8709, thanks!

@zadjii-msft commented on GitHub (Nov 22, 2021): No worries, this definitely looks like /dup #8709, thanks!
Author
Owner

@ghost commented on GitHub (Nov 22, 2021):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Nov 22, 2021): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#15944