fix measure in 4.2.2 #4
Merged
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
|
Thanks, I only have a 5.0 device currently. I will merge this tonight. |
|
Btw, can you paste the layout of the header you are using ? (Or maybe you saw the bug with the samples app ?) |
|
Yes, the sample is showing the bug as well - header view measured as
|
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.
The measure code breaks in 4.2.2 - at least thats my experience, I got a 5.0 and a 4.2.2 device and onmeasure breaks on the second one.
Turns out that
View.MeasureSpec.makeMeasureSpec(WRAP_CONTENT ...is wrong