Merged
Conversation
5 tasks
| // MARK: - Selection | ||
| private func correctSelectionAfterZWSP() { | ||
| guard selectedTextRange?.start == endOfDocument, | ||
| text == String(.zeroWidthSpace) else { |
Contributor
There was a problem hiding this comment.
Do you think we could associate the check with this configuration in common init: https://github.com/wordpress-mobile/gutenberg-mobile/pull/1552/files#diff-ad68d1bf3bf68556db4be6e6215573adL136
Just in case the character changes in the future?
Member
Author
There was a problem hiding this comment.
Good catch, pushed a change to make it more generic
This was referenced Nov 11, 2019
Merged
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
2 participants
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 original issue was that when tapping on an empty RichText, the selection was going to the end of the text by default. As we use the ZWSP character as a placeholder, the selection was after that character, and the keyboard appeared in lowercase mode.
I have a fix that corrects this, but I'm not 100% sure if this is the best place to fix it.
Fixes #1530
To test:
Some scenarios to reproduce the issue:
Update release notes:
RELEASE-NOTES.txt.