Status Update
Comments
ha...@google.com <ha...@google.com>
ja...@squareup.com <ja...@squareup.com> #2
May I ask why P3? This is blocking for me to go to prod, I'd really like some inputs about what is going on so I can either fix or build a repro to have this fixed.
ha...@google.com <ha...@google.com> #3
For the ideas on what to take a look, how do you use LazyListState.layoutInfo in your app? Will it continue growing if you comment out such usages?
ap...@google.com <ap...@google.com> #4
It happens even on screens that does not use the layoutInfo it just require many up / down flings.
LazyColumn(state = rememberLazyListState())
The only thing all screen have in common in that they have multiple item {} item{} block :(
Just in case the app is in open beta at
My main question before trying to do complex repro, is how much will it be relevant with all the recent changes in alpha 8 about Lazy stuff? And side question when
Description
It is currently difficult to draw custom spans for
Text()
becauseTextLayoutResult
does not expose any APIs for accurately reading line bounds. Considering thatAndroidParagraph
already has APIs such asgetLineAscent()
,getLineBaseline()
andgetLineDescent()
, can they be bubbled up toTextLayoutResult
?Having access to
getTopPadding()
andgetBottomPadding()
fromandroid.text.Layout
would also be helpful.AFAIK, there is currently no workaround for reading these values. Inspecting font metrics would have been one option, but that is not available either ( https://issuetracker.google.com/issues/173648606 ).