A modern programming language that makes developers happier.

kotlinlang

Hi, folks running into a issue where `collectIsPressedAsState` of InteractionSource claims pressed state even when otherwise when the item is within a scrollable lazy row/column.

```@Composable
fun InteractionSource.collectIsPressedAsState(): State&lt;Boolean&gt; {
    val isPressed = remember { mutableStateOf(false) }
    LaunchedEffect(this) {
        val pressInteractions = mutableListOf&lt;PressInteraction.Press&gt;()
        interactions.collect { interaction -&gt;
            when (interaction) {
                is PressInteraction.Press -&gt; pressInteractions.add(interaction)
                is PressInteraction.Release -&gt; pressInteractions.remove(interaction.press)
                is PressInteraction.Cancel -&gt; pressInteractions.remove(interaction.press)
            }
            isPressed.value = pressInteractions.isNotEmpty()
        }
    }
    return isPressed
}```

At some point during taps, `pressInteractions` retains a Press interaction and isn't removed.

Wondering, what is the rationale of using a list to track press state than just a boolean?

The same `MutableInteractionSource` can be passed to multiple components, which can each emit their own `Press` interactions. 

So it looks like the coroutine collecting `interactions` could be canceled before processing the release/cancel event causing the count discrepancy. Is this a known issue?

The only way that coroutine can get cancelled is if the remember call is leaving the composition, which means anything writing to it or consuming on it should also be going away, so the count not being zeroed out shouldn't matter at that point. 

Okay, the case i'm running is when the composabe is within scrollable container and occasionally, the press state is applied even after release. It doesn't use MaterialTheme and uses `DefaultDebugIndication`

From the code of `DefaultDebugIndicationInstance`, isPressed should have been true. Any tips to debug this?

```override fun ContentDrawScope.draw() {
            drawContent()
            if (isPressed) {
                drawRect(color = Color.Black.copy(alpha = 0.3f), size = size)
            } else if (isHovered || isFocused) {
                drawRect(color = Color.Black.copy(alpha = 0.1f), size = size)
            }
        }```

<@U0KMMQA20> Found it, it happens only with compose-foundation 1.9.5. It is kind of a race between `handlePressInteractionRelease` and `handlePressInteractionStart` of clickable node when the clickable element is within a scrollable container.

This seems to be fixed in compose-foundation 1.10.0 with a reference to bug 414319919
<https://android.googlesource.com/platform/frameworks/support/+/HEAD/compose/foundation/foundation/src/commonMain/kotlin/androidx/compose/foundation/Clickable.kt#2068>

Bug info isn't available, would you be able to check?