-
Notifications
You must be signed in to change notification settings - Fork 886
feat: support configurable web terminal rendering #10095
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
Conversation
14aae39
to
b996c04
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried it out and it works perfectly. I think all we have to do is tweak the e2e test startup flags to use the dom
renderer.
}>; | ||
|
||
const TerminalPage: FC<TerminalPageProps> = ({ renderer }) => { | ||
const TerminalPage: FC = () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we are getting a test failure because the test looks for HTML elements so it relies on the dom
renderer being used (see webTerminal.spec.ts
). Maybe we can start the e2e tests with dom
set as the renderer? Looks like we would do that in playwright.config.ts
if I understand correctly.
- Added a deployment option for configuring web terminal rendering. Valid values are 'webgl', 'canvas', and 'dom'.
0679c29
to
199bde3
Compare
fixes #10082