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
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 -
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!
The text was updated successfully, but these errors were encountered: