Fix issue with ZIP/Postal code field becoming first responder #4740
+66
−10
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
To fix this:
becomeFirstResponder
, we'll store a boolean to remember that it wanted to be firstResponder. When we're destroying/recreating a Section's stackView, we'll look for views with this boolean, and if any exist, we'll manually set that field as the first responder after the new stackView is ready.Motivation
MOBILESDK-1665
Testing
Existing CI tests, tested these fields in simulator (with physical keyboard) and on device:
Changelog
None, too small