Links get wrong position when they are after wide chars with canvas/webgl renderer
See original GitHub issueSee the image below. Note that it only happens to the links detected by the weblinks addon but not OSC 8 links. It also only happens to webgl and canvas renderers but the dom one.
I looked at the code a bit. It seems that the web link addon uses the character position (i.e. “哈” is counted 1 even though it is a wide character) as the the value for IBufferCellPosition.x
. Code here. Is this the correct way?
BTW, I am not sure whether this is just #2887.
Details
- Browser and browser version: Chrome 110
- xterm.js version: Tot
Issue Analytics
- State:
- Created 9 months ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Render multiple video streams in one WebGL canvas
trying 25 players/canvases. For 5 players the browser can handle it, adding more crashes the browser (tested with Chrome/Firefox). I'm wondering ...
Read more >An introduction to Three.js – The Humaan Blog
It lets you access a computer's specialised graphics hardware using JavaScript, and render the output to a webpage in a regular old <canvas> ......
Read more >Learning Pixi - GitHub
A step-by-step introduction to making games and interactive media with the Pixi.js rendering engine. - GitHub - kittykatattack/learningPixi: A step-by-step ...
Read more >How to Build a Color Customizer App for a 3D Model with ...
In this tutorial you'll learn how to create a customizer app that lets you change the colors of a 3D model of a...
Read more >Drawing graphics - Learn web development | MDN
This article will focus mainly on 2D canvas, as raw WebGL code is very complex. We will however show how to use a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@JasonXJ Should work now (plz report in https://github.com/xtermjs/xterm.js/pull/4288, if something is still totally off 🤞)
Well it still needs some more test cases, I kinda turned the whole regexp upside-down to also match unicode chars in paths (nowadays supported by all browsers), but this makes match exclusions a bit more cumbersome.
Had to fix the DOM renderer offset calc (was totally off with correct cell positions), seems there is still a one off issue at the end of underline.