IssueTracker

There is a report about it in kotlinlang Slack: https://kotlinlang.slack.com/archives/C01D6HTPATV/p1706005056105739

Thanks for the report!

The release notes documentation has been edited to clarify this change in behavior for line height.

To support non-standard text sizes, we encourage users to follow the Material design system and use a different type scale rather than changing the font size directly. Alternatively, users can overwrite the line height like so: style = LocalTextStyle.current.copy(lineHeight = TextUnit.Unspecified), or create a custom Typography entirely.

In my case, I have multiple font sizes in the same Text (using SpanStyle in AnnotatedString). There are legitimate reasons for this. For example, when combining Chinese and English (phonetic) together (for language-learning purposes).

Copying comment from M2 issue:

Looking at the Material guidelines and MDC views, it looks like the gesture only influences how the sheet is drawn. AnchoredDraggable's APIs support this, although we might want to improve the contract of the anchoredDrag method so users do not have to call settle manually.

The implementation of this lies with the Material team, reassigning for prioritization:

Here is some example code:

    /**
     * This receiver allows manipulating the sheet's offset.
     */
    interface SheetAnimationScope {
        fun seekTo(fraction: Float)
    }

    /**
     * Seek the [ModalBottomSheetState] to fractional values between [from] and [to]. This is useful
     * to integrate seeking interactions such as predictive back.
     */
    suspend fun seek(
        from: ModalBottomSheetValue = currentValue,
        to: ModalBottomSheetValue = if (from == HalfExpanded || from == Expanded) Hidden
        else if (hasHalfExpandedState) HalfExpanded
        else Expanded,
        block: suspend SheetAnimationScope.() -> Unit
    ) {
        anchoredDraggableState.anchoredDrag { anchors ->
            val startOffset = anchors.positionOf(from)
            val targetOffset = anchors.positionOf(to)
            val distance = abs(startOffset - targetOffset)
            val scope = object : SheetAnimationScope {
                override fun seekTo(fraction: Float) {
                    val newOffset = distance * fraction
                    dragTo(startOffset + newOffset)
                }
            }
            scope.block()
        }
        anchoredDraggableState.settle(0f)
    }

     PredictiveBackHandler { progress ->
          bottomSheetState.seek(to = ModalBottomSheetValue.Hidden) {
               progress.collect { backEvent ->
                    seekTo(backEvent.progress)
               }
          }
     }

CC: Dan, is this within the scope of your predictive back work in compose?

Yes! Working on this in https://android-review.googlesource.com/c/platform/frameworks/support/+/2863667.

With the approach in the CL above, ModalBottomSheet will automatically animate itself during the predictive back swipe gesture on U+.

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.compose.material3:material3:1.3.0-alpha01
• androidx.compose.material3:material3-android:1.3.0-alpha01
• androidx.compose.material3:material3-desktop:1.3.0-alpha01