verticalOffset is not correct issue #206
Open
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
Sometimes verticalOffset is not correct with getTotalScrollRange So I use extends Behavior and change this source please change this
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Sometimes verticalOffset is not correct with getTotalScrollRange
So I use extends Behavior and change this source
please change this
I can not English well.
So I can not explain in English
It's Translate
This is translator in google :
Often, the getTatalScrollRange value of AppBarLayout is not equal to the getMinOffset value, indicating that it will not move to the end.
As a result, the verticalOffset value of the OnOffsetChangedListener does not match the getTotalScrollRange value even though the scroll has been moved to the end.
So there are a lot of problems in creating my app.
After correcting as above, it is correct operation.
Please consider modifying