Haxe

meanwhile I submitted a PR for the HTML5 pointer events change

I didn't take out some of the older chunks of redundant code, just commented them in case it broke something, but can't see anything going wrong with the test app

interesting... what is browser support like?

pretty much universal since something like Chrome 40

https://developer.mozilla.org/en-US/docs/Web/API/Pointer_events

cool - well.. ill run your branch though component explorer and see how it fares

try it with the touch emulation in browser responsive modes if you don’t have a touch device to test with

I’ve no idea how mobile browsers simulate a right click, or if they even do, so I left it alone as a mouse event

press for a while i think... i think browsers are generally smart enough to send a right click if you press and hold... i think so anyway

there was a `contextmenu` event somewhere in the haxeui-html5 code, but had something else feeding it events, didn’t test changing it in case I broke something

ah, yeah, that might be it actually, its contextmenu rather than some discrete right click event

does that event also trigger for a mouse right click though?

i think thats the "trick"... ill have to take a look and see if thats the case.... cant remember off hand

but there is defo "right click" on haxeui-html5, but i _think_ its something like that, ie, abuse context menu

hmm somewhere there's an invalid cast on my test app

I don't think the EventMapper MOUSE_TO_TOUCH and TOUCH_TO_MOUSE are necessary either if pointer events are being used

since under PE, they are all one type of pointer, just with extra possible fields set

is there a reason that (the HTML DOM event) `MouseEvent.buttons` is used over `MouseEvent.button` for handling mouse button presses?

https://api.haxe.org/js/html/MouseEvent.html#button
this seems to line up better with the actual DOM event API for both Mouse Events and Pointer Events

```0: Main button pressed, usually the left button or the un-initialized state
1: Auxiliary button pressed, usually the wheel button or the middle button (if present)
2: Secondary button pressed, usually the right button
3: Fourth button, typically the Browser Back button
4: Fifth button, typically the Browser Forward button```

it's used in ComponentImpl.hx:660 and ScreenImpl.hx:479