Status Update
Comments
ma...@google.com <ma...@google.com>
jo...@google.com <jo...@google.com> #3
Thanks for the report!
se...@google.com <se...@google.com>
ma...@gmail.com <ma...@gmail.com> #4
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 style = LocalTextStyle.current.copy(lineHeight = TextUnit.Unspecified)
, or create a custom Typography
entirely.
se...@google.com <se...@google.com>
se...@google.com <se...@google.com> #5
se...@google.com <se...@google.com>
de...@gmail.com <de...@gmail.com> #6
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).
se...@google.com <se...@google.com> #7
I have updated the ticket linked to be public. It is a tracker for migrating the internal popup functionality to a custom window view for easier access to window flags.
se...@google.com <se...@google.com> #8
Interestingly, upon investigation this is only an issue on APIs above 29. Regardless of using popup or a generic android view. It seems to be documented here:
continuing to investigate but the solution unfortunately does not seem so straight forward.
sk...@gmail.com <sk...@gmail.com> #9
I thought that
se...@google.com <se...@google.com> #10
I think it's possibly related in that the same use case: Using compose text fields on new windows appears to have the same effect whether it be a PopupWindow, an AbstractComposeView or in their case DialogFragment. So it makes me suspicious that this may be an issue with TextField instead of the windowing logic. The change you linked moves the BottomSheet to a custom view instead of the UI popup but does not alone fix this bug.
se...@google.com <se...@google.com> #11
This issue which extends to any custom windows seems to have been resolved with:
Waiting on that change to land to proceed on this issue.
ja...@gmail.com <ja...@gmail.com> #12
de...@gmail.com <de...@gmail.com> #13
For me the modal bottom sheet works now. The only bug is, that the cursor drag indicator is shown above the cursor instead of below.
ap...@google.com <ap...@google.com> #14
Branch: androidx-main
commit 7545cec3617ab5d1ea83d66822bc094e7f03c562
Author: José Figueroa Santos <serniebanders@google.com>
Date: Wed Apr 19 16:04:18 2023
[Material3][gradle] Update compose dependencies to 1.4.2
Upgrade needed to intake the following bug fix:
Bug: 268380384
Bug: 272483584
RelNote: ModalBottomSheet now can display IME keyboard
Test: Manual
Change-Id: Idc5082008acb547cac2100a69cab4be7db85f50f
M compose/material3/material3/build.gradle
M compose/material3/material3/samples/src/main/java/androidx/compose/material3/samples/BottomSheetSamples.kt
se...@google.com <se...@google.com>
am...@gmail.com <am...@gmail.com> #15
ju...@google.com <ju...@google.com> #16
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.compose.material3:material3-android:1.2.0-alpha02
Description
Jetpack Compose version: M3 1.1-alpha6
Jetpack Compose component used: ModalBottomSheet
Android Studio Build: IC-231.6471.13
Kotlin version: 1.8.10
Steps to Reproduce or Code Sample to Reproduce:
Focus the text field.
The keyboards gets opened behind.