IssueTracker

Hi,

I also see my text cut off when I set maxLines = 2. Is it the same issue?

  Box(
    modifier =
      Modifier.size(
        width = 108dp,
        height = 34dp,
      ),
    contentAlignment = Alignment.Center,
  ) {
    BasicText(
      text = "text text text",
      maxLines = 2,
      autoSize = AutoSize.StepBased(minFontSize = 1.sp, maxFontSize = 13.sp, stepSize = 0.2.sp),
    )
  }

Project: platform/frameworks/support
Branch: androidx-main
Author: Jossi Wolf <jossiwolf@google.com>
Link:      https://android-review.googlesource.com/3450389

Fix TextAutoSize bug with maxLines = 1

Fix TextAutoSize bug with maxLines = 1 
 
We were overcaching the paragraphIntrinsics in MultiParagraphLayoutCache when mutating the style. For `AutoSizeStepBased` instances with biased windows (more values smaller/bigger than the optimal), this could result in performing layout with outdated intrinsics, and thus an outdated style and font size, without surfacing this in the TextLayoutResult. 
 
Test: New MultiParagraphLayoutCacheTests and manual testing 
Relnote: Fixed a bug in BasicText with TextAutoSize and maxLines set to 1. 
Fixes: 376834366 
 
Change-Id: Ic0450c763c5d764492995b44ee1fe570246a9689

#2, yeah, that's the same issue.

Thanks @jo...@google.com for fixing this! Do you know when the fix would be available for g3 apps?

Moving the internal discussion offline. The bug is fixed and the fix available in snapshot builds. We will comment on this issue when the bug fix is included in a release.

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

• androidx.compose.foundation:foundation:1.8.0-beta01
• androidx.compose.foundation:foundation-android:1.8.0-beta01
• androidx.compose.foundation:foundation-jvmstubs:1.8.0-beta01
• androidx.compose.foundation:foundation-linuxx64stubs:1.8.0-beta01

Re #7:

If infinite animation work is almost done, please go ahead and finish. We are in desperate need for help deprecate AnimationClockObservable. My plate is overflowing with API finalization for Animatable and AnimatedVisibility right now, which won't leave enough time for the clock deprecation. :(

Could Jelle loan us a helpful hand on this high priority deprecation, if he's not swamped with critical issues himself? (It is high priority because API changes as such must be done before beta.)

The infinite animation work is in state of completion now, and I'll start working on migration from AnimationClockObservable today.

My apologies for not responding earlier, I had to take a few days off due to circumstances. Things are better now though!

Thank you so much Jelle! I really appreciate that.:)