Skip to content
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

5.0 refactor for the flipper probably broke true type for the elevated card #3499

Closed
bebenins opened this issue Mar 19, 2024 · 1 comment · Fixed by #3500
Closed

5.0 refactor for the flipper probably broke true type for the elevated card #3499

bebenins opened this issue Mar 19, 2024 · 1 comment · Fixed by #3500
Labels
Milestone

Comments

@bebenins
Copy link
Contributor

Bug explanation

Once I switched my app to 5.0 release, I have the following weird issue with Cards.
image

From @Keboo
So there are a couple things going on there.
The App.xaml is lacking the default resource dictionary so the default styles are not being picked up. This does expose a bit of a problem with the base Card control, but this is also not really a case that is expected to work.
But setting this also doesn't fix it. With 5.0.0 there are two available styles for the Card control. MaterialDesignOutlinedCard and MaterialDesignElevatedCard (the default). It looks like the problem only appears with the MaterialDesignElevatedCard I suspect it is related to the drop shadow, but I will need more time to look into exactly what is causing it. If you need a quick fix, switch to the outline style and you should see it working.
Attached is a minimalist test project.
MD_5.0_test.zip

Version

5.0.0

@bebenins bebenins added bug evaluation required Items is pending review or evaluation by the team labels Mar 19, 2024
@Keboo Keboo added this to the 5.1.0 milestone Mar 19, 2024
@Keboo Keboo removed the evaluation required Items is pending review or evaluation by the team label Mar 19, 2024
@Keboo Keboo mentioned this issue Mar 21, 2024
@bebenins
Copy link
Contributor Author

@Keboo already tested it and it works nicely. There was one other performance issue that was resolved as a result of this fix (was waiting to see it before logging).
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants