Fixed
Status Update
Comments
sg...@google.com <sg...@google.com>
ap...@google.com <ap...@google.com> #2
Project: platform/frameworks/support
Branch: androidx-main
Author: Shalom Gibly <
Link:
Date picker input mode validation error height
Expand for full commit details
Date picker input mode validation error height
Fix the bottom padding at the DatePicker in an input-mode when a
validation error displays an error text.
The fix ensures that the height of the component stays unchanged when
that happens.
Fixes: 280462363
Test: Added to DateInputTest
Relnote: "Fixed an issue with the DatePicker in input mode where
validation errors could cause the component's height to change"
Change-Id: I2e229559964acd9522e8a696bb0e89698c20bdd9
Files:
- M
compose/material3/material3/src/androidInstrumentedTest/kotlin/androidx/compose/material3/DateInputTest.kt
- M
compose/material3/material3/src/commonMain/kotlin/androidx/compose/material3/DateInput.kt
Hash: fb4f052613c3e49f8aa1c45cb150fc5dde9f2e29
Date: Thu Oct 10 14:30:26 2024
pr...@google.com <pr...@google.com> #3
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.compose.material3:material3:1.4.0-alpha03
androidx.compose.material3:material3-android:1.4.0-alpha03
androidx.compose.material3:material3-jvmstubs:1.4.0-alpha03
androidx.compose.material3:material3-linuxx64stubs:1.4.0-alpha03
Description
Jetpack Compose version: compiler 1.4.6
Jetpack Compose component used:
androidx.compose.material3:material3:1.1.0-rc01
Android Studio Build: Giraffe
Kotlin version: 1.8.20
Steps to Reproduce or Code Sample to Reproduce: Use a simple
androidx.compose.material3.DatePicker
composable, and let the user enter a date which is invalid for the given date validator.Nothing more needs to be done, and as soon as the last digit is added and the input is considered invalid, the bottom spacing is completely removed and the error message hugs the bottom.
This is a bug specifically because without the error message the spacings look perfectly fine.
Since this library is on the 1.1.0-rc right now, it'd be nice for this to be fixed before the real release if at all possible.
I have attached a before/after screenshot, along with a little video showing this interaction.