Closed JGeek00 closed 3 days ago
I have no idea who from the Flutter team thought that making this breaking change is a good idea.
Why haven't they passed dynamicSchemeVariant: DynamicSchemeVariant.fidelity
by default? Ew.
Closing as dupe (e.g. #591)
Package
dynamic_color
Existing issue?
What happened?
Expected vs actual result:
I think this started happening with Flutter v3.22, because previously I didn't had to define the
cardTheme
,popupMenuTheme
, andnavigationBarTheme
to match the colors of the Material 3 specification, but currently if I don't define that parameters with the correct background color, the background color of that components is rendered white.If I don't use the dynamic color scheme and instead I use a normal color, it works fine.
This happens because now the
surfaceContainer
color is completely white (I mean rgb(0, 0, 0)), and according to the Material 3 specification, that color is the one that has to be used for the container background.https://m3.material.io/components/cards/specs
https://m3.material.io/components/menus/specs
https://m3.material.io/components/navigation-bar/specs
If I define that colors on the teme with
surfaceTint
instead of withsurfaceContainer
, the correct color is applied.Relevant log output
No response