playcanvas / playcanvas/engine
Different behavior between touch and mouse input with UI element when `stopPropagation` is used
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 16.8k
- Forks
- 2k
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 222
Description
Example project: https://playcanvas.com/editor/project/997802
There is a full screen UI element that takes the input event and calls stopPropagation.
The expectation is that the the user cannot move the orbit camera.
With mouse events, this works as expected. On touch devices/events it does not.
We should have consistency between the two.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked example project and reproduce the difference between mouse and touch input when a full-screen UI element calls stopPropagation. Trace the two input paths and verify that the orbit camera cannot move in either case; done means consistent propagation behavior for mouse and touch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100