This repository was archived by the owner on Nov 17, 2025. It is now read-only.
Issue #12 - Fixing wrong offset with newlines #22
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
…e content offset doesn't intentionally get set to a negative value which is causing the text to jump in a perfectly sized text view with a single line.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Fixing wrong offset with newlines and ensuring the content offset doesn't intentionally get set to a negative value which is causing the text to jump in a perfectly sized text view with a single line.
Not taking any credit for these fixes since they come from other people's suggestions. But there hasn't been any pull requests to update the main repository with these changes. So figured I would do one 👍