Skip to content
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

Strange rendering issue on Chrome #1061

Open
spurin opened this issue Jan 13, 2023 · 1 comment
Open

Strange rendering issue on Chrome #1061

spurin opened this issue Jan 13, 2023 · 1 comment

Comments

@spurin
Copy link

spurin commented Jan 13, 2023

Hi @tsl0922

Firstly, thanks for your efforts on the project, love ttyd!

I've already resolved this issue but lost a good day troubleshooting it on a bit of a wild goose chase so just want to raise it here for awareness in case this comes up again. Please close the issue when you're ready.

Am using ttyd on a ubuntu 22.04 container image and sometimes when I vim a file, it wasn't clearing the terminal as expected. I'd see half of the terminal display as well as the edited file on the screen.

The issue only seemed to affect Chrome, Safari was okay.

I tested ttyd with the renderType=dom and that fixed it for Chrome (albeit with a broken prompt). When I went to check Chrome the version at the time was 'Version 105.0.5195.102 (Official Build) (arm64)' which dates to around Nov 2022. It auto updated and the behaviour went back to as expected without an implicit renderType option (my current chrome version is now Version 109.0.5414.87 (Official Build) (arm64)).

It really looked quite bizarre. So much so that I captured a video that I was going to send to you just before running the update. Here it is for reference -

https://www.dropbox.com/s/zb9toy8pxvqwbcx/strangeRenderType%20Issue.m4v?dl=0

Again, thanks for ttyd!

@spurin spurin added the bug label Jan 13, 2023
@tsl0922
Copy link
Owner

tsl0922 commented Feb 22, 2023

ttyd uses xterm.js to render terminal outputs.

The default renderer is WebGL2, sadly and sorry I'm not an expert for it.

To get the problem solved quickly, maybe you should open the issue in xterm.js's issue tracker (if you can reproduce it with xterm.js demo).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants