Respect charSpace when wrapping text with maxWidth#3996
Open
cycsmail 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
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.
When
maxWidthis set,doc.text()wraps viasplitTextToSize(), but the per-callcharSpacenever reached the width measurement used for wrapping, so text wrapped as ifcharSpacewere 0 and then overflowedmaxWidthonce the spacing was rendered.charSpacefromtext()intosplitTextToSize()charSpace / fontSizeper character in the standard-font width branch (same units the embedded-font branch already uses)maxWidthand that a widercharSpacewraps into more linesNo public API change, so
types/index.d.tsis untouched. The new spec fails without the fix and passes with it;npm run test-nodepasses (468 specs, 4 pre-existing pending) and prettier is clean on the changed files.Fixes #3299