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

No problem!

1. Let me circle back on that to confirm, but I believe the Landscape mode follows the same logic to distill to direct input mode or full-screen instead of this modal in your screenshot.
2. Yes the 48x48dp touch target is the new accessible requirement that all platforms will need to meet.

Basically, with a small screen size and high text sizes and high screen zoom the "OK" and "Cancel" buttons goes off the screen, making them nearly impossible to click for the users that need high sizes. See attached screenshot.

"Cancel" and "OK" buttons are not visible also when you increase font size to 200% and display size to 320dp width (see attachment)

This violates WCAG guildelines and Google's own guidelines https://support.google.com/accessibility/android/answer/12159181

Tested on Pixel 7 Pro emulator API 34

androidx.compose.material3:material3:2023.10.00

For the "OK" and "Cancel" issue, you can add a Modifier.weight to the DatePicker in the DatePickerDialog as a temporary workaround. I'm going to push a fix that will do that internally inside the DatePickerDialog and will work for nesting a DatePicker or DateRangePicker.

DatePickerDialog(
    onDismissRequest = {...},
    confirmButton = {...},
    dismissButton = {...}
) {
    DatePicker(state = datePickerState, modifier = Modifier.weight(1f))
}

Hi Christian. Since Dillon is on leave do you mind forwarding this to the appropriate designer, thanks!

Thank you Josė. There are a couple of related scaling issues which I propose we look at all together. For the moment I am assigning this to ticket to Andrew, and included May in CC for awareness.

Hi Andrew, do you gave an update on guidance here?

Hi Christian, connecting to you as I believe you are currently looking into the 360dp width layouts. Please feel free to re-assign or reach out if there's anything I can do to help. Thank you!

We are currently working on general layout updates to the date picker, as we will most likely need to support screen width up to 320dp.

Please stay tuned.