You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Images are pretty rare at least in my usage patterns, we would save a bunch of work by not creating/attaching/resizing the canvas until the first time it's needed
I know I'm blocking on xtermjs/xterm.js#4577 and will move this over when that goes in, trying to catch up 😅
The text was updated successfully, but these errors were encountered:
We could even go one step further and remove the canvas for long living terminals, once the storage gets emptied (thus all image notions got finally removed from scrollback etc). Ofc this would create a tiny burden for canvas recreation upon the next image (which is a rather rare use case). Not sure if this helps much, it would at least save some resources on very big terminals. In the end there is not much use for a transparent canvas on top of everything else, if there is nothing to show on it at all.
Images are pretty rare at least in my usage patterns, we would save a bunch of work by not creating/attaching/resizing the canvas until the first time it's needed
I know I'm blocking on xtermjs/xterm.js#4577 and will move this over when that goes in, trying to catch up 😅
The text was updated successfully, but these errors were encountered: