After thinking a bit longer ... I think the old behaviour was crooked to start with and completely broke the "click" semantics after the fix the blocking issue
The whole idea of the click was to support a click-in-cell-coordinates, that is simulate the feel of a button. That makes sense only if the release happens in the same cell as the release (the implementation most probably relies on that fact somewhere anyway, didn't check though). Whoever used it for something else, mis-used it. So we are safe to fix, hehe
So changed the behaviour to fire a clicked on release if the release happens in same cell. It's decided in an overridable method to allow subclasses to change. If we get a loud uproar, we can add a system/app property to allow unconditional click-on-release. (which was the old incorrect behaviour) More elaborate logic could be added if requested - that would be handled in a new feature issue.
wiki is unavailabe, forum is more-or-less unwritable ... sigh