Strange doubleclick on title behavior about labwc

[winteriscariot]

iirc, the first time i noticed, I had clicked something in the window, then immediately went to drag it, but it disappeared instead.

so in my particular case, could maybe not register that second click if it's a click-and-hold?

[Consolatis]

Yes, AFAIR we indeed only use the cursor position of the second click to determine the target.
Is this something that results in unwanted behavior? E.g. is this an issue outside of manually reproducing it?

If yes we could potentially store the first target and on the 2nd click compare the two targets and if they differ do not call the bound action.

[winteriscariot]

The only reason I noticed this behavior is because it was unexpected, and a window disappeared when I didn't expect it to. This is also not the way it behaves in openbox, fwiw, so maybe worth restricting it to the titlebar imo.

[Consolatis]

iirc, the first time i noticed, I had clicked something in the window, then immediately went to drag it, but it disappeared instead.

That sounds like something that totally can happen. Lets fix this.

[tokyo4j]

I experienced this problem too when I first started using labwc. Setting <mouse><doubleClickTime> (default is 500) to 200 mitigated this, but more sophisticated solution would be ideal.

[johanmalm]

Does #1659 solve this?

[Consolatis]

Should be fixed in latest master. Thanks for bringing this up.