You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a StackOverflow question about this issue?
I have searched StackOverflow
What happened?
The FullScreenLayoutBase component in the @Composable library currently allows users to specify a custom backgroundColor. However, it has been observed that when a custom backgroundColor is provided, it overrides the background surface color defined by MaterialTheme. This behavior may lead to unintended UI inconsistencies and may not align with user expectations.
Expected Behavior
The backgroundColor property of FullScreenLayoutBase should work as expected, allowing users to set a custom background color when needed. However, when a value of Color.Unspecified is provided for backgroundColor, it should respect the background surface color defined by MaterialTheme, ensuring a consistent UI experience.
Proposed Solution
I propose that the backgroundColor property of FullScreenLayoutBase should default to Color.Unspecified, which will ensure that it respects the background surface color defined by MaterialTheme. Users can still override it with a custom color when needed.
Relevant logcat output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Is there a StackOverflow question about this issue?
What happened?
The
FullScreenLayoutBase
component in the@Composable
library currently allows users to specify a custombackgroundColor
. However, it has been observed that when a custombackgroundColor
is provided, it overrides the background surface color defined byMaterialTheme
. This behavior may lead to unintended UI inconsistencies and may not align with user expectations.Expected Behavior
The
backgroundColor
property ofFullScreenLayoutBase
should work as expected, allowing users to set a custom background color when needed. However, when a value ofColor.Unspecified
is provided forbackgroundColor
, it should respect the background surface color defined byMaterialTheme
, ensuring a consistent UI experience.Proposed Solution
I propose that the
backgroundColor
property ofFullScreenLayoutBase
should default toColor.Unspecified
, which will ensure that it respects the background surface color defined byMaterialTheme
. Users can still override it with a custom color when needed.Relevant logcat output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: