My assumption was containers would not only mask objects inside of them. but also touch events.
If not, display.containers probably should have a isHitTestMasked property like image masks do.
In the use case shown in the attached image, the image inside the container on the right gets the touch event before the image on the left due to the creation order, even though the touch event is outside the container holding the image.
Hmm, that’s a bug.
Touch events should only register inside the container’s bounds.
That’s what I thought too… If I had my preference, it would only mask the “began” phase. That way if an object had stage focus you could move it out of the container bounds, just not select it outside of the container bounds.
Make sense?
Hmm, that’s a bug.
Touch events should only register inside the container’s bounds.
That’s what I thought too… If I had my preference, it would only mask the “began” phase. That way if an object had stage focus you could move it out of the container bounds, just not select it outside of the container bounds.
Make sense?