-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(android): background color/image handling improvements #10451
feat(android): background color/image handling improvements #10451
Conversation
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Dimitris - Rafail Katsampas.
|
a8a9e6c
to
9524783
Compare
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Dimitris - Rafail Katsampas.
|
dba175a
to
747753a
Compare
db104bf
to
b2c2d03
Compare
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.