Fixing issue where acknowledgement content was scrolled up slightly #43
Conversation
This file contains 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
vtourraine
added a commit
that referenced
this pull request
Nov 14, 2015
Fixing issue where acknowledgement content was scrolled up slightly
|
Thanks for the PR, Levi, and I apologize that it look me so long to merge it in (especially for a one-line fix). Nice catch. 👍 |
|
@vtourraine No worries. Thanks for taking the pull. :) |
|
@vtourraine Would you mind adding this to a new Cocoapod version please? |
|
I will, in general I’m simply waiting for a couple of days after any change on In the meantime (and someone might find it useful beyond this case here), you can always use |
|
There you go: version |
|
Many thanks. |
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.
While the default value of a UITextView's contentOffset should be
CGPointZeroI was seeing (iOS 9) the content scrolled slightly up, and under the navigation bar. Resetting thecontentOffsetaftertextContainerInsetcorrects this issue.