Enable Dynamic Enabling / Disabling without External Feature Detection #77
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Detail
The library before any manual enabling performs a feature detection to check whether the
webkit
like scroll behaviour property even works, effectively checking if the library will be used at all or not:This works well for situations where you only need this enabled once, but in our use case we need to be able to disable or enable iNoBounce only when a particular overlay is opened, which means this feature detection on the libraries IIFE construction is ignored. This coupled with the
0.1.6
version of the library seems to break Android scrolling entirely. The change here is to expose a boolean that can be rechecked when ever the consumer wishes to enable / disable the iNoBounce behaviour without worrying it will affect non-ios like devices.As an example this might be used like this: