onMouseDown, onPointerDown and probably more events do not work as intended about core HOT 5 CLOSED

From what I tested it behaves like that when the button is a child of a div. It looks like the events are handled by the button instead of a div, and since you do not perform TrickleDown the event is probably stopped by the button, just registering an empty event.

<div onPointerDown={() => {console.log("onPointerDown")}}>
  <button>
    Button
  </button>
</div>

from core.

The newest version of core and renderer now allow TrickleDown variant of all events like onPointerDownCapture

from core.

I tried this with UIToolkit (I think that is how you tested it too). For div, it works as expected:

Except onPointerCancel because I don't know how to test it. Also onPointerUp and onMouseUp don't fire if you leave the element when holding the mouse down.

For button it is as you said. onPointerDown doesn't work probably because Unity handles that internally. According to this forum thread the event should be registered with TrickleDown, and ReactUnity does not do that. It is similar to capture in browsers. So I will add a capture variant to every event.

Drag events are for editor UI only. They don't work in runtime afaik. A while ago I did a prototype on how they work, so they should be working (in editor).

I don't know why the div works different for you. Can you see any difference that may cause it?

from core.

That works! Thank you :)

But I have to argue if that would not be confusing to have so many different events. At the end of the day should perform the same exact action, and there is almost no difference for the end user.

from core.

React for Web also has the same naming convention for capture events (for example onClick and onClickCapture). Since UIToolkit is inspired by HTML, I think it is acceptable to have this.

There may be significant differences for the end user, and I can't know which variant the user needs. So, I think it is better to present both options. For example, parent element will receive the event first in capture phase, wherease in bubble phase child element will receive the event first.

Closing this as solved.

from core.