Better CommonJS/AMD support
Add setDisabledInputMethods() to the public API to enable input methods to be enabled & disabled during the lifecycle of an FTScroller instance
Add options to disable pointer and focus event listeners
Ensure event handlers are set after removing them :)
Split _toggleEventHandlers into dedicated set... and remove..., to ensure that all listeners are removed correctly when setDisabledInputMethods() is called with new values
In _updateScroll, adjust the current scroll based on the instance's scrollResponseBoundary setting. This means the scroll doesn't jump to the gesture position immediately, instead, the scroll position lags behind by the scroll response boundary value.
Ensure that click events are added correctly based on the input method filtering
Remove all event listeners unconditionally
Only add click event listener if all the click-triggering input methods are disabled
Merge pull request #75 from rdsubhas/master

Better CommonJS/AMD support, Fix browserify issues
Make setDisabledInputMethods() definition more closely match the original instance options, not requiring boolean values
Add a comment
Merge pull request #83 from ftlabs/inputmethodsApi

Inputmethods API
Merge remote-tracking branch 'origin/master' into scroll-start-jank
Merge pull request #84 from ftlabs/scroll-start-jank

Try to improve the user experience when a scrollResponseBoundary of a reasonable size is set.
Recent changes in Windows event capture handling allow us to finally move to event bubbling instead of capturing, leading to nicer behaviour of nested scroller; this updates the approach in Issue #13 and Issue #71.
Merge pull request #88 from ftlabs/bubblingevents

Enable event bubbling instead of capture for better nested scrollers
Merge remote-tracking branch 'origin/master' into paginatedSnapFromOutsideBounds