Closed kzgolden-pba closed 11 years ago
I have made a test for this case and it seems to work properly.
Gestures does not avoid the event to be bubbled up, because they always return undefined. This feature should be implemented.
Webkit scroll works "Ember 0.9.81" on the following test, perhaps the failure is coming from other side.
@kcgolden, may you reproduce your example in order i can test it.
I am having trouble reproducing an independent case demonstrating this issue though it is definitely happening in some proprietary code I am dealing with.
The behavior is simple:
What is the functionaility of a gestureDelegate when it disables the touchHoldEnd method? Does it only set it to undefined or something more?
You should take a look at the Gesture Manager._invoke_event.
It checks if they are some conditions ( gesture.isEnabled, gestureDelegate, delegateRules, appGestureManager ) to pass the event to the gesture or skip it and bubble the event to the parentView.
If you remove the touchHoldEnd method, the view has not assign any gesture. It seems like the gesture does not allow to bubble up the event, but i tested it and worked well.
You can also debug the EventDispatcher.
Closing this issue because inactivity.
I'm attempting to use the following css properties on a childview:
overflow-y: auto !important; -webkit-overflow-scrolling: touch;
If the parentView has a function for touchHoldEnd, the above property will not work on child views. This is even the case when I used a gestureDelegate to disable the touchHoldEnd at a time when the childview with scrolling is present. I can tell that gestureDelegate is functioning because the touchHoldEnd function does not get called on the parentView when it's disabled. However, only by completely removing the touchHoldEnd method from the parent can I get the touch scrolling functionality on the child view.