Autocorrect no longer loses styles & iOS 11 workarounds contained. #767
Conversation
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
…nditionally executed.
This was referenced Oct 13, 2017
jleandroperez
approved these changes
Oct 13, 2017
Contributor
jleandroperez
left a comment
jleandroperez
left a comment
There was a problem hiding this comment.
Works as advertised!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description:
This issue fixes #750 and #761.
We're wrapping our iOS 11 workarounds so that they're only executed in iOS 11 +.
We're fixing autocorrect so that it will no longer lose the font styles.
Testing: