tracking: Events support
Closed this issue · 2 comments
marc2332 commented
This issue tracks the support for events.
onclick
- implemented
- screen coordinates
- element coordinates
- global
onmousedown
- implemented
- screen coordinates
- element coordinates
- global
onmouseover
- implemented
- screen coordinates
- element coordinates
- global
onmouseleave
- implemented
- screen coordinates
- element coordinates
onmouseenter
- implemented
- screen coordinates
- element coordinates
onmouseup
- implemented
- screen coordinates
- element coordinates
- global
onwheel
- implemented
- y scroll
- x scroll
keydown
- implemented
- Composable characters
- Modifiers
keyup
- implemented
- Composable characters
- Modifiers
onglobalclick
- implemented
- screen coordinates
ontouchcancel
- screen coordinates
- element coordinates
- Finger ID
- Force
- global
ontouchend
- screen coordinates
- element coordinates
- Finger ID
- Force
- global
ontouchmove
- screen coordinates
- element coordinates
- Finger ID
- Force
- global
ontouchstart
- screen coordinates
- element coordinates
- Finger ID
- Force
- global
onpointerdown
- screen coordinates
- element coordinates
- Mouse type
- Touch type
- global
onpointerup
- screen coordinates
- element coordinates
- Mouse type
- Touch type
- global
onpointerover
- screen coordinates
- element coordinates
- Mouse type
- Touch type
- global
onpointerenter
- screen coordinates
- element coordinates
- Mouse type
- Touch type
onpointerleave
- screen coordinates
- element coordinates
- Mouse type
- Touch type
Tropix126 commented
marc2332 commented
Should
onclick
also be fired along with touch events? From what i've seen, browsers typically treat the "click" event as an abstraction over a group of behaviors that could trigger something (for example, if enter or space is pressed while an element is focused).
I also asked myself that question. I will see what other GUI libraries do 🤔 I just opened #201