Hello! Is the behavior observed here expected, or ...

# compose

[Guilherme Delgado]

Hello!
Is the behavior observed here expected, or could it be a bug? Specifically, when using a Scaffold with a TopAppBar and a PullToRefreshBox, and passing innerPadding to a LazyVerticalStaggeredGrid (or any other layout that only composes and lays out visible items on screen), we need to do this:

Scaffold(
    topBar = {...}
) { innerPadding ->
    PullToRefreshBox(
        ...,
        indicator = {
            Indicator(
                modifier = Modifier
                    .align(Alignment.TopCenter)
                    .padding(top = innerPadding.calculateTopPadding()),
                isRefreshing = isRefreshing,
                state = pullState
            )
        }
    ) {
        LazyVerticalStaggeredGrid(contentPadding = innerPadding, ...) {...}
    }
}

To ensure both work correctly. If the calculateTopPadding is ignored, the pull-to-refresh functionality doesn’t work properly. Is this the intended solution or is there a better way to achieve this?

[Chrimaeon]

So the grid view is not a child of the refresh box?

[Guilherme Delgado]

it’s a child yes (code updated)

[Chrimaeon]

Pass the inner padding to the refresh box and not the grid.

[Guilherme Delgado]

bot how, cannot be through padding, I want the list to be behind the top bar, thus the contentPadding

[Guilherme Delgado]

using calculateTopPadding as Indicator padding ✅

[Guilherme Delgado]

using calculateTopPadding as PullToRefreshBox padding ❌

[Guilherme Delgado]

padding.png

[Chrimaeon]

Then you have to do it the way you did.

[Guilherme Delgado]

Ok, just wanted to check if I was on the right track 🙂, thanks!