Status Update
Comments
sg...@google.com <sg...@google.com>
al...@gmail.com <al...@gmail.com> #2
Project: platform/frameworks/support
Branch: androidx-main
Author: Louis Pullen-Freilich <
Link:
Adds OverscrollEffect#withoutDrawing and OverscrollEffect#withoutEventHandling
Expand for full commit details
Adds OverscrollEffect#withoutDrawing and OverscrollEffect#withoutEventHandling
These APIs allow overscroll to have events dispatched to it by one component, and rendered in a separate component.
Fixes: b/266550551
Fixes: b/204650733
Fixes: b/255554340
Fixes: b/229537244
Test: OverscrollTest
Relnote: "Adds OverscrollEffect#withoutDrawing and OverscrollEffect#withoutEventHandling APIs - these APIs create a wrapped instance of the provided overscroll effect that doesn't draw / handle events respectively, which allows for rendering overscroll in a separate component from the component that is dispatching events. For example, disabling drawing the overscroll inside a lazy list, and then drawing the overscroll separately on top / elsewhere."
Change-Id: Idbb3d91546b49c1987a041f959bce4b2b09a9f61
Files:
- M
compose/foundation/foundation/api/current.txt
- M
compose/foundation/foundation/api/restricted_current.txt
- M
compose/foundation/foundation/integration-tests/foundation-demos/src/main/java/androidx/compose/foundation/demos/OverscrollDemo.kt
- M
compose/foundation/foundation/samples/src/main/java/androidx/compose/foundation/samples/OverscrollSample.kt
- M
compose/foundation/foundation/src/androidInstrumentedTest/kotlin/androidx/compose/foundation/OverscrollTest.kt
- M
compose/foundation/foundation/src/commonMain/kotlin/androidx/compose/foundation/Overscroll.kt
Hash: f64e25b7a473c757d080521e7dd97b3f6670f60d
Date: Fri Nov 01 18:43:56 2024
ap...@google.com <ap...@google.com> #3
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.compose.foundation:foundation:1.8.0-alpha06
androidx.compose.foundation:foundation-android:1.8.0-alpha06
androidx.compose.foundation:foundation-jvmstubs:1.8.0-alpha06
androidx.compose.foundation:foundation-linuxx64stubs:1.8.0-alpha06
ma...@google.com <ma...@google.com> #4
Thanks for pointing out the spec discrepancy! This has been fixed.
As for the minimumInteractiveComponentSize()
issue, a workaround is to use Modifier.offset
on the icon, but we will explore options to make this common use case more intuitive.
pr...@google.com <pr...@google.com> #5
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.compose.material3:material3:1.2.0-beta02
androidx.compose.material3:material3-android:1.2.0-beta02
androidx.compose.material3:material3-desktop:1.2.0-beta02
od...@gmail.com <od...@gmail.com> #6
Can we ask why this was closed? We are finding that the trailing padding has issues even after the applied fix and the workaround posted here. Note the following reproducible code and screenshots.
@Preview(widthDp = 403)
@Composable
private fun ListItemTrailingPaddingIssue() {
ListItem(
overlineContent = {
Text("Overline content")
},
headlineContent = {
Text("Headline content reaches to trailing content")
},
supportingContent = {
Text("Supporting content")
},
trailingContent = {
IconButton(
// We've applied the modifier "workaround". However, note the large padding left between the leading
// and trailing content because the offset doesn't change or move the actual padding of
// the trailing content
// https://issuetracker.google.com/issues/305342674#comment4
modifier = Modifier.offset(
y = (-12).dp,
x = 12.dp,
),
onClick = {},
) {
Icon(
imageVector = Icons.Default.Delete,
contentDescription = "Delete button",
)
}
},
)
}
@Preview(widthDp = 403)
@Composable
private fun ListItemWithoutTrailingPaddingIssue() {
ListItem(
overlineContent = {
Text("Overline content")
},
headlineContent = {
Text("Headline content reaches to trailing content")
},
supportingContent = {
Text("Supporting content")
},
trailingContent = {
Icon(
imageVector = Icons.Default.Delete,
contentDescription = "Delete button",
)
},
)
}
da...@mullvad.net <da...@mullvad.net> #7
Can verify this issue is still not fixed in latest Material3 version 1.2.0. Workaround addresses the issue but creates a new issue with the trailing padding being to large as stated by
Description
I was trying to use the
ListItem
composable from material3 and noticed a couple of issues withtrailingContent
leaving more space than expected at the end.First issue
After checking the specs , I believe that
ListItemEndPadding
is set to the wrong value. It should be16.dp
not24.dp
.Second issue
If, for example, I try to recreate the "One-line lists" and use a
CheckBox
in the trailing content lambda,ListItem
will add a16.dp**
padding to the end. Unfortunately, a clickableCheckBox
usesminimumInteractiveComponentSize()
, and the reserved space will increase from24.dp
(CheckBox size) to48.dp
, adding12.dp
to the already existing16.dp
fromListItem
.Right now I think it's not possible to recreate the examples from the specs that have a "Secondary Action area" like a
CheckBox
,IconButton
, or anything small with a minimum touch target size added. Text "100+" examples are different since they don't need to be clickable.Steps to reproduce
Run a composable with this content:
Instead of 16.dp, we get:
Apologies if this is working as expected. All the
ListItem
examples useText
as thetrailingContent
and I think an example withCheckBox/IconButton
could be very helpful, because I don't see what the correct approach is when using other types of content. Thank you.