Is there some parameters to help the scrollindicat...

# compose-wear

[Tolriq]

Is there some parameters to help the scrollindicator calculation that I'm missing or is this a bug ? (Thread)

[Tolriq]

Video of the scrollbar being filled then becoming smaller when scrolling down, while all the items are visible so there should not be different item size issues.

Screen_recording_20240513_182937.webm

[Tolriq]

Code is a simple

ScreenScaffold(scrollState = scalingLazyColumnState) {
        ScalingLazyColumn(scalingLazyColumnState) {
            item {
                ResponsiveListHeader(contentPadding = firstItemPadding()) {
                    Text()
                }
            }
            item {
                ToggleChip()
            }
            item {
                ToggleChip()
            }
            item {
                ToggleChip()
            }
        }
    }

[Tolriq]

Ok so no it happens on any small lists due to the large content padding not being taken in account 😞

[yschimke]

It's possibly a bug with content padding, if so you should raise it.

[yschimke]

But there are known limitations with LazyList including SLC for PositionIndicator. I'll dig out the existing bug.

[yschimke]

OK, public bug I found from Jan 22 is closed as fixed. I found an internal one still open. So feel free to raise one.

[yschimke]

But the logic for PositionIndicator state is very simple and won't handle subtle changes as you scroll. like 3 out of 5 items being on screen, becoming 4 out of 5.

[yschimke]

or mixing large and small items.

[yschimke]

Consider this screen with some large and some small items (alternatint grey and black)

[yschimke]

image.png

[Tolriq]

Yes I know the common limitations they are always the same on lazy stuff, but in that case all the items where on screen hence the question.

[yschimke]

Probably worth raising a bug with repro code.

[Tolriq]

Checking the code it's the contentpadding but that would require a complete change of the logic, so will raise bugs when I'm at the details for the ui.

[yschimke]

For the bigger problem, it does seem solvable once you understand the structure of your content.

[Tolriq]

The repro code is here, it's caused by the horologist stuff adding the padding.

[Tolriq]

But will do a full round of report when I reach a mature enough state.