floating-scroll

• Add the method destroyDetached for finding and destroying “zombie” instances of the widget.
• Fix the issue Amphiluke/handy-scroll#14.

Introduce the scrollbar orientation option. From now on, the plugin allows making vertical floating scrollbar too (feature requested in #19).

• Fix scroll bar invisibility issue on Mac OS (Amphiluke/handy-scroll#3)
• Fix widget syncing issue (#17)
• Update dev dependencies

This release brings no changes in source code, it just fixes a vulnerability introduced by the old version of clean-css.

• Fit widget height to the native scroll bar height when needed.
• Update dependencies to fix vulnerabilities reported by npm.

Fix the same issue as reported in Amphiluke/handy-scroll#2.

• Fix eventual bug with widget re-rendering in Chrome.
• Sync widget scroll position on update invocations.
• Refactoring of the plugin internals.

Fix the issue #6 (thanks @kwetts for reporting).

Uglify build output files to make the sources for production even smaller.

• Port sources from the jquery-plugins repo. If for some purpose you want to get commit history for older plugin versions, you can extract it from that old repo.
• Make things npm-compatible (Amphiluke/jquery-plugins#8).

• A new auto-initialisation feature is added.
• Plugin sources have been re-written in ES6.
• Support of “ancient” browsers (IE 8 and older) is dropped (if you still keep supporting them, please use floatingScroll 2.3.3 instead).
• Old deprecated plugin’s alias attachScroll and the event adjustScroll have been completely removed (use floatingScroll and update.fscroll instead).

Repair forgotten stuff in v2.3.2 (for republishing to npm) 😕

Add a feature allowing floating scroll bar to be more “unobtrusive” (see the Tips section for more details)

Make floating-scroll a Bower package. Requested in #11.

Handle a special case of a floating scroll bar within a positioned box (popups etc.) Requested in #8. Find out the details in the section Special cases of the docs, or play with a demo.

• Fix for the issue #7 (thanks to @hngu).
• Minor refactoring.

Fix for the issue #6

Fix for the issue #4 (thanks to @AdrianPiechota)

Fix for the issue #2 (thanks to @AdrianPiechota)