-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow xterm.js to exist and receive/send data before it's attached to the DOM #266
Labels
type/enhancement
Features or improvements to existing features
Comments
Sounds legit. Would it make sense to export the renderer into its own module for this? |
Ideally, not sure how difficult that is right now |
This was referenced Sep 18, 2016
Tyriar
added a commit
that referenced
this issue
Feb 1, 2017
Since the Terminal can be used now before being attached, we should check element on destroy. Related to #266
Tyriar
added a commit
to Tyriar/xterm.js
that referenced
this issue
Feb 1, 2017
Since the Terminal can be used now before being attached, we should check element on destroy. Related to xtermjs#266
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In v1.6 of VS Code the newly introduced Terminal API will allow processes to exist before the actual terminal panel/element is created. While this is currently possible, xterm cannot be initialized until the element exists, which means the output before the element is attached is lost. It would be good if everything was functional only no rendering took place until
open
is invoked.The text was updated successfully, but these errors were encountered: