IssueTracker

1. Can you please confirm that the Text you are using is from the Material 3 lib (not accidentally from M2).
2. Can you post a video for the second problem you've mentioned? That may help explaining the issue.

Thanks!!

Hello,

1. I use only Material 3 Components.
2. I have attached two videos with both problems.

Thanks for the quick reply.

For #1 - Right now, the app bar snaps to expand only on a single case when a fling downwards ended with partially expanded app bar.

We will soon work on implementing a motion spec for all cases where an app bar stops mid way, so this kind of behavior will be eliminated (i.e. Medium and Large app bars will always snap to expand or collapse). I'll keep this bug open until this is implemented.

For #2 - I could not reproduce the issue both on an emulator and on a real device. Considering what I wrote on #1, there is a slight possibility that a small downward fling was detected and the app bar was attempting to snap to expand, but I didn't witness any of it.

Can you post your code, or something equivalent, for ScreenWithColumn()? I assume it's something simple like what we have at https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:compose/material3/material3/samples/src/main/java/androidx/compose/material3/samples/AppBarSamples.kt;l=300, but will need to verify we didn't miss anything here.

The code I used for the video is the following:

@Composable
fun ScreenWithColumn() {
    LazyColumn(
        horizontalAlignment = Alignment.CenterHorizontally
    ) {
        items(50) {
            Text(text = it.toString())
            Divider()
        }
    }
}

Again, only material 3 components.

The second problem can only be reproduced when scrolling quickly and when you then reach the exact moment that the title bar is extended by a few millimetres. Then it collaps again and pulls everything up with it.

I'm afraid this is still not reproducible (see video).

Since I'm running on the latest, there is a chance we had some foundational changes that fixed it, so please wait till the next release to see if this is still happening.

As mentioned above, I'll keep this issue open mainly for the motion issues you've noted above.

Thanks!

Regarding the second problem:
Thanks, I will wait for the next version. From your video, it also looks like something has already happened there, as the collapsing looks better (more "fluid"?) than it does for me at the moment.

Good day,
with the new alpha release (16) of Material 3 I can still reproduce the second problem.

Ah, that's unfortunate. I still can't reproduce this issue here. Is your Gradle locked to an older Compose foundation version (i.e. not :compose:material3:material3)?

For #1: I just pushed https://r.android.com/2172933 that takes care of the app-bar snapping, and you should no longer experience a case where the app bar is not fully expanded or fully collapsed after a drag/fling is completed.

I have implemented androidx.compose.material3:material3:1.0.0-alpha16 which is currently the latest version.

Thanks. I was referring to the other dependencies on Compose. Specifically, make sure you are depending on 1.3.0-alpha02 or above.

Thank you, I had used version 1.2.1. Maybe it would be a good idea to write at Material3 that a newer version is also necessary for the other compose librarys. (https://developer.android.com/jetpack/androidx/releases/compose-material3#declaring_dependencies)
Now I can no longer reproduce the #2 issue.

A quick other question, as it was asked above whether I use the Text Composable from the Material or Material3 Library. Is it safe to use components from Material if they do not exist in Material3 (e.g. SwipeToDismiss) or is there a risk of problems?

Glad this worked out. We consider this as unsafe. Please don't mix M2 and M3, as they are quite different and you may end up with unexpected results.

Ok, thank you for all your work! I have opened a FR for SwipeToDismiss. I hope that's correct, because you can actually only create bugs...