This repository was archived by the owner on Jul 9, 2026. It is now read-only.
Repository navigation
Persist keyboard as you switch from one block to another - #296
Merged
Merged
Conversation
The default behavior had FlatList blurring field every time you tapped outside them, which meant they were being blurred twice and losing the keyboard.
mzorz
approved these changes
Nov 29, 2018
mzorz
left a comment
Contributor
There was a problem hiding this comment.
Tested, found minor glitches that I'll document separately.
LGTM ![]()
This was referenced Nov 29, 2018
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Another take at #291. Most of the changes are in wordpress-mobile/react-native-aztec#84 but this also sets
keyboardShouldPersistTapstoalwaysin theFlatList.The default behavior had FlatList blurring field every time you tapped outside them, which meant they were being blurred twice and losing the keyboard.
To test, follow the steps in #291, and confirm the keyboard stays up. A known issue is that if you tap on a non-text block (image, unsupported), the current text field will keep focus, but that's a different task in #197