Open OvermindDL1 opened 7 years ago
Not fully tested yet, but it looks like this might also happen if a swipe is given a direction one way, but not the other (like being able to swipe left but not right), then swiping the accepted way to start a swipe, then swipe it off into the other way (like swiping left, then far right in the prior example).
Yep there is a bug there, thanks for the report !
In a few places
this._currentAction
is accessed without checking if it is null first, such as in_swipeUpdate
,_swipeEnd
,_applyGestureTranslation
(called by_swipeStart
), and_applyRubberBand
(called by_applyGestureTranslation
). Normally you'd think this would not be an issue, however putting<swipe-action>
in a Polymer app-drawer, for example, causes the drawer being slide one way (a way that the swipe elements ignore, say the drawer is on the left and can be slid left, and the swipe-action can be swiped right) to cause the swipe-action to receive '_onTrackcallbacks, which then causes it to access an
undefined`this._currentAction
, thus crashing the event handling and causing exceptions in the scripts.