LinearProgressIndicator shape [222964817]

Fixed

Bug

Status Update

No update yet.

Description

sz...@gmail.com

created issue #1

Mar 6, 2022 07:38PM

Jetpack Compose release version: 1.1.1
Android Studio Build: Bumblebee Patch 2
Kotlin version: 1.6.20

Please make the shape of LinearProgressIndicator modifiable as well which shows the progress..
Currently only the "frame" is modifiable via the clip modifier.

Thank you!

Comments

so...@google.com <so...@google.com> Mar 10, 2022 06:52PM

Assigned to je...@google.com.

pa...@gmail.com <pa...@gmail.com> #2Aug 5, 2022 05:10AM

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

te...@gmail.com <te...@gmail.com> #3Sep 27, 2022 11:25PM

Thanks for the report!

ma...@google.com <ma...@google.com> Nov 28, 2022 06:26PM

Reassigned to ma...@google.com.

ma...@google.com <ma...@google.com> Nov 29, 2022 06:36PM

Accepted by ma...@google.com.

ma...@google.com <ma...@google.com> #4Dec 8, 2022 08:30PM

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.

ap...@google.com <ap...@google.com> #5Dec 8, 2022 10:55PM

deleted

ap...@google.com <ap...@google.com> #6Dec 8, 2022 10:55PM

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).

sz...@gmail.com <sz...@gmail.com> #7Dec 9, 2022 12:53AM

Thats great! Thanks Max

ma...@google.com <ma...@google.com> Dec 12, 2022 06:47PM

Marked as fixed.

na...@google.com <na...@google.com> #8Jan 11, 2023 08:11PM

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

androidx.compose.material:material:1.4.0-alpha04
androidx.compose.material3:material3:1.1.0-alpha04