I noticed that if I started a click and then i mouse over a composable with either `hoverable()` or ...

# compose

[Alex Styl]

I noticed that if I started a click and then i mouse over a composable with either hoverable() or .onPointerEvent(PointerEventType.Enter/Exit) the event is never triggered.

Is this a bug or intended? How can i get hovered events for where the pointer is in such case?

Screen Recording 2024-10-15 at 15.08.38.mov

[Alex Styl]

val interactionSource = remember { MutableInteractionSource() }
    val hovered by interactionSource.collectIsHoveredAsState()

    Row(Modifier.fillMaxSize()) {
        Box(Modifier.weight(1f).fillMaxHeight())
        Box(
            modifier = Modifier.weight(1f).fillMaxHeight().background(Color.LightGray).hoverable(interactionSource),
            contentAlignment = Alignment.Center
        ) {
            Text("Hovered? = ${hovered}")
        }
    }

[mohamed rejeb]

Try using pointer input Modifier instead

[mohamed rejeb]

It looks like the same issue is happening with using pointerInput

[Alex Styl]

yup. mentioned in the OP

[Alex Styl]

Openned an issue @ https://youtrack.jetbrains.com/issue/CMP-6860/hoverable-doesnt-work-if-click-and-drag-from-outside

[Ruckus]

I would guess this is expected behavior. At least, that's my experience from other frameworks. Once you click and hold on a control, all mouse/touch events are sent to that control until the click is released. Setting up drop behaviors usually requires some sort of special handling involving a blackboard to transfer data.

[Ruckus]

https://developer.android.com/develop/ui/compose/touch-input/user-interactions/drag-and-drop

[Alex Styl]

interesting. wasn't aware that the typical way of events being handled