fix: updated field multiline to have enough width #2208
Merged
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.
The basics
The details
Resolves
Fixes #2095
Proposed Changes
Updated the width to have 1px extra on each side.
Reason for Changes
From what I can tell, this issue is created by rounding in the browser in different contexts. With Zoom = 100%, this worked as intended for me before the fix. Zooming in, though, I noticed the calculated component ended up as
?.06
and the text area ended up as?.05
. Essentially, there's barely not enough space for the content, so it wraps to the next line. (See screenshots below.)Test Coverage
No unit tests needed, though here's what I manually tested:
Before at 125% zoom: (Note: the last character wraps to a new line)

After at 125% zoom:

Documentation
N/A
Additional Information
What's the expected behavior when the text is long enough to produce an ellipsis? It seems like it wrapping to a new line when the text is too wide in this context might be expected.
Long text with "...":

Corresponding long input text wrapping:
