Fixed
Status Update
Comments
ph...@gmail.com <ph...@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
co...@google.com <co...@google.com>
sg...@google.com <sg...@google.com>
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
sg...@google.com <sg...@google.com>
fu...@gmail.com <fu...@gmail.com> #4
I encountered this issue, on what version of material 3 has this been fixed?
fu...@gmail.com <fu...@gmail.com> #5
This is my workaround for this issue
MaterialTheme(
colorScheme = MaterialTheme.colorScheme.copy(
//The color you want for the second top app bar
surface = MaterialTheme.colorScheme.primary
),
typography = MaterialTheme.typography
) {
LargeTopAppBar(
modifier = Modifier.background(MaterialTheme.colorScheme.primary),
title = {
Text("Wednesday")
},
)
}
na...@google.com <na...@google.com> #6
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.compose.material3:material3:1.0.1
androidx.compose.material3:material3:1.1.0-alpha02
pa...@gmail.com <pa...@gmail.com> #7
This issue is still present in material3:1.0.1 - moving to 1.1.0-beta01 fixed it for me.
da...@gmail.com <da...@gmail.com> #8
i am also getting the same issue, is there any solution for this ?
Description
Jetpack Compose version: 1.3.0-beta03
Jetpack Compose component used: androidx.compose.material3:material3:1.0.0-beta03
Android Studio Build: Android Studio Dolphin | 2021.3.1 | Build #AI-213.7172.25.2113.9014738
Kotlin version: 1.7.10
Problem:
If a custom container color is applied to MediumTopAppBar or LargeTopAppBar, the bottom half of the AppBar gets default color.
Reason:
This is because of the color is only applied to the top section:
AppBar.kt, line 1166