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
fix(card): update background to use the same as item #19602
Conversation
uses item background but falls back to the background of the content
Hi, thanks for the PR, is there a way i can check this right now before getting merged and released so i can tell you if it fixes the problem ? |
@shadoWalker89 Sure! Here is a dev build, but this is based off of our See the changelog for what is in 5.0 so far: https://github.com/ionic-team/ionic/blob/master/CHANGELOG.md |
So this fix will not be included in the ionic 4 ? So this is what i did, Also i updated the I run it on the device, the card background is now fixed but the image is still flickering |
This change will not be reflected in version 4.x? |
I think there's some confusion here. This PR is only to update the card background to use the following as the default:
Prior to this it didn't fallback to the background color of the app. However, it is currently possibly to set it to do this by setting it on the
Whether or not it fixes #19140 was just a possibility but this PR is not intended to fix that issue, only the issue of it not falling back to the background color. This will go into 5.x as this is not critical (it has a workaround). |
@brandyscarney Thank your for your answer and explanation in details. But please could you check out the image problem that i mentioned in my last answer ? Thanks |
Pull request checklist
Please check if your PR fulfills the following requirements:
npm run build
) was run locally and any changes were pushednpm run lint
) has passed locally and any fixes were made for failuresPull request type
Please check the type of change your PR introduces:
What is the current behavior?
Card backgrounds are transparent which causes issues
What is the new behavior?
Does this introduce a breaking change?
Other information