TextInput horizontal padding does not update on iOS

[davidlongest]

Description

What happens

When changing horizontal padding (paddingRight, paddingLeft, paddingHorizontal) on a TextInput during focus change, the text in the TextInput view should reflect the padding change.
What makes this especially odd is that changing any vertical padding by more than the height of the view (for height 20 can have left and right of 10 or horizontal of 20) makes the text respect the horizontal padding changes.

What I expected

When changing the horizontal padding, the text should change position to respect the padding.

Reproduction Steps

Using the sample code below...

1. Note the two TextInput fields have space between the text and border
2. Click or tap the first field to give it focus
3. Note that text changes to red, but there is still padding between the text and border
4. Open the inspector and click the focused field
5. Note that the content area (blue) fills the entire text view (showing 0 padding)
6. Click the unfocused field
7. Note the padding area (green) fills up the empty area next to the text

Sample Code

Run the code below on iOS and switch focus between the two text inputs. Opening the inspector shows that the padding is updated, but the text itself doesn't actually update its position.

https://snack.expo.io/S1B3TZv7Z

Solution

The ideal fix is to make sure horizontal padding updates are respected, even if it is on one axis. The issue doesn't seem to lie within what React thinks the view should look like, but instead with the actual iOS view code.

Additional Information

• React Native version: 0.45.0
• Platform: iOS 10.2
• Development Operating System: macOS Sierra 10.12.5
• Build tools: XCode 8.2.1

[davidlongest]

Verified still happens in 0.46.0

[atlanteh]

Yep, happens to me too

[inevermore]

Happens to me too in 0.47

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions.

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "For Discussion" or "Good first issue" and I will leave it open. Thank you for your contributions.

[stale]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.