@firasdib Ah I see, I understand that it's how the regexes are working under the hood, but it still isn't intuitive to hover over the second surrogate of the character when the character itself is rendered as one, it is literally a 1-pixel wide hitbox to get the hover for the 2nd surrogate.

          @firasdib Ah I see, I understand that it's how the regexes are working under the hood, but it still isn't intuitive to hover over the second surrogate of the character when the character itself is rendered as one, it is literally a 1-pixel wide hitbox to get the hover for the 2nd surrogate.

What if instead you made it display both surrogates for hovering the multi-surrogate character? i.e. hovering over the example character used 𐌐 in a non-Unicode regex flavor could show a unified hover like this:

Text - matches literally (case-sensitive) the character pair: � with index 55296₁₀ (D800₁₆ or 15400₈) followed by � with index 57104₁₀ (DF10₁₆ or 157420₈)

This way the regex decomposition of the displayed Unicode characters is easily viewable and also prevents potentially misleading users unaware of Unicode semantics into thinking their Unicode characters equal to only the first surrogate they see on the current hover.

Originally posted by @jhmaster2000 in https://github.com/firasdib/Regex101/issues/2061#issuecomment-1565036374

firasdib / Regex101

@firasdib Ah I see, I understand that it's how the regexes are working under the hood, but it still isn't intuitive to hover over the second surrogate of the character when the character itself is rendered as one, it is literally a 1-pixel wide hitbox to get the hover for the 2nd surrogate. #2088