fix(textinput): resolve placeholder truncation on initial render #816
+2
−2
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
Problem
The
placeholderViewfunction intextinput.gowas creating a rune slice with sizem.Width+1. Whenm.Widthis 0 during initial render, this created a slice of length 1, truncating multi-character placeholders to just their first character.Solution
m.Width+1tomax(len(m.Placeholder), m.Width+1)to ensure it can always hold the full placeholderlen(m.Placeholder)instead oflen(p)Test plan
All tests show full placeholder text immediately on render, no more truncation.
Fixes #779