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
I am new to using xtermjs. I am not sure whether the terminal instance can call the open() method multiple times. According to the official documentation and #1323, I tried it. When I removed the dom and mounted again, and used terminal.open(), xterm did not render after the second open.
I am not very deep into the browser side of the code, @Tyriar has more insights here. Still I think it is not possible to move an already DOM-attached terminal to another DOM node by calling open again.
@Tyriar Do we need an attach/detach cycling for the DOM hooking? It never came to me before, that someone would want to move an existing terminal to another DOM node, so this might be just a wild idea of limited use. Loosely linked or more generalized to this would be support of a copy ctor like const term2 = new Terminal(term1), where the new terminal could start over in DOM-detached mode, but has inherited all VT-related settings/data. This has some intersections with the serialize addon, so might not be worth either the trouble.
I am new to using xtermjs. I am not sure whether the terminal instance can call the
open()
method multiple times. According to the official documentation and #1323, I tried it. When I removed the dom and mounted again, and usedterminal.open()
, xterm did not render after the second open.Details
Steps to reproduce
Reproduce
I'm sorry if there's something wrong with my usage
The text was updated successfully, but these errors were encountered: