de4028336a
When a Snap was disabled it stopped listening to the events, but if a drag gesture was being performed it was kept as active. Thus, when the Snap was enabled again move events were handled as if the Snap had never been disabled, causing the gesture handling to continue where it was left. When the Snap for the navigation bar is disabled by an app it could be as a result of a different gesture being recognized by the app (for example, a vertical swipe) once both gestures have started. In that case when the other gesture ends and the Snap is enabled again any pointer movement will cause the navigation bar to slide until an "up" event is triggered again (obviously not the desired behaviour). Due to all this now when the Snap for the navigation bar is disabled by an app the current drag gesture for the navigation bar is ended. Note that this was added as a parameter to "Snap.disable()" instead of done unconditionally to keep back-compatibility with the previous behaviour (probably not really needed as it is unlikely that any app is using the Snap library relying on that behaviour... but just in case). Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> |
||
---|---|---|
.. | ||
autosize | ||
backbone | ||
base64 | ||
blueimp-md5 | ||
bootstrap | ||
clipboard | ||
davclient.js | ||
DOMPurify | ||
es6-promise | ||
handlebars | ||
jcrop | ||
jquery | ||
jquery-migrate | ||
jquery-ui | ||
jsTimezoneDetect | ||
marked | ||
moment | ||
select2 | ||
snapjs | ||
strengthify | ||
underscore | ||
zxcvbn | ||
.gitignore | ||
core.js |