entering a surface first generates a leave event

[rhizoome]

… on the surface being entered, which confuses some applications. An important one is almost unusable: It resets input when menus close.

Systeminfo: https://tpaste.us/7oWO

wev | grep surf

This shows what happens when I move the mouse into the wev surface.

[14:     wl_keyboard] leave: serial: 1488; surface: 3
[13:      wl_pointer] leave: surface: 3
[09:     xdg_surface] configure: serial: 1487
[14:     wl_keyboard] enter: serial: 1532; surface: 3
[13:      wl_pointer] enter: serial: 1537; surface: 3, x, y: -4.906250, 1144.730469
[09:     xdg_surface] configure: serial: 1534

Other compositors will only generate enter events on entering and leave events on leaving.

Specs here and here suggest that enter and leave should only create one event:

• not repeated ones
• and definitely not conflicting ones

[xzn]

wev uses buffered stdout so the output is simply showing up late. Which application is being confused exactly?

[rhizoome]

You are right. I know the issue is very complicated and I already wrote a wall of text. I thought I have now boiled it down to a simple answer.

stdbuf -i0 -o0 -e0 wev shows that I am wrong. But I have an application that gets way too many FocusOut messages, yes it is actually xwayland. that is why I was glad I found a something simple.

But even this is

stdbuf -i0 -o0 -e0 xev | grep Focus is correct. So what is happening with the Juce application is very strange.

Here is the original discussion, I deleted the walls of text tough, when I closed it, because I thought is all wrong. And the above is the reason.

#11325

[rhizoome]

Wow, I so many red hearings! I give up. I have some kind of LD_PRELOAD hack that makes no sense, but still fixes the problem.

[rhizoome]

@xzn I cleanup my original post: #11325