fix: preserve terminal glyph rendering#10
Open
CoderLuii wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
node-ptyoutput from rawBufferchunks with a streaming UTF-8 decoder before sending text over the WebSocket.web-terminal-disable-webglfallback for systems where WebGL glyph rendering still shows black squares.Why
HolyClaude hit this through the baked Web Terminal plugin: CoderLuii/HolyClaude#40 reports unreadable terminal output with black squares, missing letters, and broken box drawing while running
task-master init.PR #9 points at the same UTF-8 boundary class, but it also includes scroll and tmux/dtach session persistence changes. This PR keeps the rendering fix narrow so it can be reviewed separately.
Testing
npm installnpm run build