-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
Transition the default terminal renderer to use WebGL and polish setting #106202
Comments
Before actioning this we should make |
Let's switch the default and add webgl support detection in this iteration if we have time in debt week. |
We may not end up removing the canvas renderer as some device (eg. iPad) don't support webgl2. Still we can keep this open and tracking finishing up the transition to the webgl renderer:
|
The plan is to remove the canvas renderer in favor of the basically better in every way webgl renderer, plus the plan for xterm.js is to remove the canvas renderer eventually. I think renaming the setting for this would also be a good idea, from:
To:
This would help with discoverability of the feature and hides implementation details that don't matter for the end user like "dom" and "webgl".
Currently
auto
is the same ascanvas
and doesn't do anything in particular. For the new setting it should do something like this:When using the webgl renderer, fps is measured similar to the canvas renderer now and will drop down to the dom renderer (cache choice) if they are much lower than expected (indicating some chromium/gpu interaction issue).
The text was updated successfully, but these errors were encountered: