`onPointerEvent` gets triggered even when its Composable is covered by another one. I have a dialog ...

# compose-desktop

[Marcin Wisniowski]

onPointerEvent gets triggered even when its Composable is covered by another one. I have a dialog displaying on top of an element, but clicking on the dialog also interacts with the element behind the dialog. What would be the proper way to handle this? I expected events to not get delivered if it's covered by something.

[Marcin Wisniowski]

I fixed this by also adding a dummy onPointerEvent that does nothing on the dialog, which seems to consume the event so that it doesn't reach the element behind it.

[Alexander Maryanovsky]

Reproducer please

[Marcin Wisniowski]

When scrolling over the green area events get printed, even though the grey area that has the onPointerEvent is covered.

Repro.kt.cpp

[Alexander Maryanovsky]

Scroll events are supposed to do that. Otherwise you would not be able to scroll a container with any content inside it.

[Alexander Maryanovsky]

But not in a dialog

[Marcin Wisniowski]

Same for Move events though, I guess it's also intended?

[Alexander Maryanovsky]

Mouse move I think no. Not sure.

[Alexander Maryanovsky]

Although… how would a button with text work if not?

[Alexander Maryanovsky]

So I guess that’s also expected

[Marcin Wisniowski]

And same for Press events, which is certainly not ideal 😄

[Marcin Wisniowski]

Since I'm ending up clicking stuff that's behind and not visible

[Alexander Maryanovsky]

Yeah