fix: textfield prefix design feedback#10060
Merged
Merged
Conversation
|
Build successful! 🎉 |
devongovett
approved these changes
May 12, 2026
yihuiliao
approved these changes
May 12, 2026
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.
Closes
Design feedback that space between small prefix, such as the first example in the textfield docs, was too large. It was leftover from when I thought the prefix was only going to be wf icons or text.
✅ Pull Request Checklist:
📝 Test Instructions:
Go to docs, there shouldn't be a large amount of space between the '#' and the placeholder in the first example of Textfield's prefix example.
🧢 Your Project: