fix: fix android: foreground bug - #19
Open
Eric-Jim-Lab wants to merge 1 commit into
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
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.
We discovered a CC (Configuration Compatibility) Bug in your library. This issue is caused by the abnormal display of
android:foregroundin Android API levels below 23. As shown in the image below (To make the presentation more evident, we specifically chose an example during the image loading process), when the software runs on API level 22, clicking the image does not trigger any response, whereas when running on API level 23, the click effect appears as expected. The example shown below is just one sample; the otherimg_coverinstances exhibit the same effect.Our repair tool recommends replacing
android:foregroundwithandroid:backgroundto ensure compatibility with lower API levels. Furthermore, we have tested this fix on multiple higher API levels, and it has proven to be effective. Below is the result after applying the fix. Looking forward to your reply.