{"shas":[["7cce0c5573ad593b17302082e936b10f568551a4","0b646148fc066c4e93af2e511bb2baf66741bfdf@adobe.com","Fixes for issue 1464 - No way to stop a link from being followed with some custom event (tap, taphold)\n\njquery.mobile.vmouse.js:\n\n\t- Modified triggerVirtualEvent() so that it returns the virtual event instead of the isDefaultPrevented() result of the virtual event.\n\n\t\t- Updated all references to triggerVirtualEvent() that relied on the boolean return value to instead check the isDefaultPrevented() call on the event now returned.\n\n\t\t\t- Updated mouseEventCallback() to propagate the iDefaultPrevented(), isPropagationStopped(), and stopImmediatePropagation() values from the virtual event on to the  original mouse event.\n\n\t\t\tjquery.mobile.event.js\n\n\t\t\t\t- Modified the \"taphold\" trigger code to create a new $.Event() instead of passing the stale vmousedown event.\n\n\t\t\t\t\t- Added clearTapTimer() which is called from a new vmouseup binding, to prevent the timer from firing between the tie the finger/mouse goes up and the click event is dispatched.\n\n\t\t\t\t\t- Added some propagation tests for the \"tap\" event. Tests for \"taphold\" will have to wait until we fix the problem where multiple taphold timers are fired off when an element and one of its ancestors is bound to taphold.","Kin Blas"]],"ref":"refs/heads/master","size":1,"head":"7cce0c5573ad593b17302082e936b10f568551a4","push_id":41550766}