IssueTracker

Able to reproduce it with the following sample, the middle item, has a small area that cannot be clicked:

@Preview
@OptIn(ExperimentalMaterial3Api::class,
    ExperimentalFoundationApi::class, ExperimentalMaterialApi::class
)
@Composable
fun HorizontalPagerTabsSample() {
    val scrollBehavior = TopAppBarDefaults.pinnedScrollBehavior(rememberTopAppBarState())

    Scaffold(
        topBar = {
            TopAppBar(
                title = { Text(stringResource(R.string.horiz_pager_title_tabs)) }
            )
        },
        modifier = Modifier
            .fillMaxSize()
            .nestedScroll(scrollBehavior.nestedScrollConnection),
        ) { padding ->
        val pages = remember {
            listOf("Home", "Shows", "Movies")
        }

        Column(
            Modifier
                .fillMaxSize()
                .padding(padding)) {
            val coroutineScope = rememberCoroutineScope()

            // Remember a PagerState
            val pagerState = rememberPagerState()

            TabRow(
                // Our selected tab is our current page
                selectedTabIndex = pagerState.currentPage,
                indicator = { tabPositions ->
                    TabRowDefaults.Indicator(
                        Modifier.pagerTabIndicatorOffset(pagerState, tabPositions) { it }
                    )
                }, modifier = Modifier
            ) {
                // Add tabs for all of our pages
                pages.forEachIndexed { index, title ->

                    Tab(
                        text = { Text(title) },
                        selected = pagerState.currentPage == index,
                        onClick = {
                            // Animate to the selected page when clicked
                            coroutineScope.launch {
                                pagerState.animateScrollToPage(index)
                            }
                        }
                    )

                }
            }

            HorizontalPager(
                pageCount = pages.size,
                state = pagerState,
                // Add 16.dp padding to 'center' the pages
                contentPadding = PaddingValues(16.dp),
                modifier = Modifier
                    .weight(1f)
                    .fillMaxWidth(),
                userScrollEnabled = false
            ) { page ->
                val refreshScope = rememberCoroutineScope()
                var refreshing by remember { mutableStateOf(false) }
                var itemCount by remember { mutableStateOf(15) }

                fun refresh() = refreshScope.launch {
                    refreshing = true
                    delay(1500)
                    itemCount += 5
                    refreshing = false
                }

                val state = rememberPullRefreshState(refreshing, ::refresh)
                // Our content for each page
                Box(Modifier.fillMaxSize()
                    .pullRefresh(state, enabled = true)) {

                    
                    PullRefreshIndicator(refreshing = refreshing, state = state,
                            modifier = Modifier
                                .align(Alignment.TopCenter))
                   
                    Text(
                        text = "Page: ${pages[page]}",
                        style = MaterialTheme.typography.titleMedium,
                        modifier = Modifier.align(Alignment.Center)
                    )
                }
            }
        }
    }
}

Looks like this is happening because PullRefreshIndicator uses a Surface, which internally uses Modifier.pointerInput {} to block siblings from seeing input. In this particular case it's a problem because we offset the indicator off screen, and the indicator is below the tabs, so it ends up being displayed on top of the tabs and intercepting input.

We should consider:

a) whether we can fully remove the indicator when it's not visible anyway b) not using surface, and hence not blocking input

I think the best solution here is to replace the Surface with just a box with modifiers, to avoid blocking input - and keep it always being emitted. That way we won't break cases like using Modifier.onGloballyPositioned, which might not even be emitted until the indicator is shown

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.compose.material:material:1.5.0-alpha02

Still occurs using material = 1.8.0.

Using:

androidxCompose = "1.6.0-alpha01"
androidxComposeMaterial3 = "1.2.0-alpha03"

androidx-compose-material = { group = "androidx.compose.material", name = "material", version.ref = "androidxCompose" }
androidx-compose-material3 = { group = "androidx.compose.material3", name = "material3", version.ref = "androidxComposeMaterial3" }

and it works fine