Skaldebane
11/23/2024, 4:24 PMcontentPadding
parameter to BasicTextField
in Compose 1.8?
I've filed an issue here a while ago: https://issuetracker.google.com/issues/302599627Skaldebane
11/23/2024, 4:25 PMDaniel Weidensdörfer
11/23/2024, 9:28 PMStylianos Gakis
11/23/2024, 9:48 PMDaniel Weidensdörfer
11/23/2024, 9:55 PMSkaldebane
11/23/2024, 10:29 PMscrollable
modifier inside the decoration box gives the text field infinite height, which:
1. Forces the whole text field to get rendered, foregoing any current (or upcoming) optimizations.
2. Makes the scrollState
parameter of the text field effectively useless, always staying at 0
.Skaldebane
11/23/2024, 10:32 PMHalil Ozercan
11/23/2024, 11:50 PMscrollable
modifier in decorator, the behavior is undefined. We are committed to addressing this concern since it's a shortcoming of the decoration API. I'm afraid it won't be in 1.8
though.Skaldebane
11/24/2024, 12:09 AMcontentPadding
?
As an aside, one other blocker to using the new fields is AnnotatedString
support, are those being worked on for 1.8 or delayed for a later release?Skaldebane
11/24/2024, 12:14 AMBringIntoViewRequester
alongside the results of onTextLayout
and TextFieldValue.selection
to keep the cursor on screen, but it's not very complicated, and aside from potential performance issues, it works pretty well, on both the new and old text fields (I still use the old text fields when I need AnnotatedString
).