feat(android): background color/image handling improvements #10451
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.
PR Checklist
What is the current behavior?
There are cases when android native background is not unset when background or background color is set to null.
Also, blank shadow rules seem to cause weird behavior as there can be a view with
box-shadow: none
by default and that view will have its default drawable removed.Another thing that was tracked during tests is that cached drawable seems to be broken since ever because it's set to the wrong instance.
This is a continuation of #9615.
What is the new behavior?
This patch takes care of the remaining background handling problems and adds a few android-specific helper functions to get rid of deprecated
setColorFilter
calls and duplicate code here and there.