OverlayScrollbars Version 1.10.2

Improvements:

• Fixed a bug where the overflow wasn't calculated properly on the newest firefox in some cases.
• #166 updated package.json in all wrapper components.

Angular:

• Fixed a bug where the usage of a MutationObserver in connection with zone.js freezed the browser. #168

OverlayScrollbars Version 1.10.0

Improvements:

• The host element of a textarea element now applies the focus class if the textarea get focused.
• Improved event handling & management (passive & preventDefault e.g. non-passive events)
• The plugin now recognizes already existing DOM (helpful in component wrappers & PHP / SSR Sites)

React:

• Fixed a bug where elements which were generated through iteration of a list wasn't applied correctly.
• Is using now existing DOM, so React generates the DOM, not the plugin.

Vue:

• Fixed a bug where it wasn't possible to use v-for as direct children.
• Is using now existing DOM, so Vue generates the DOM, not the plugin.

Angular:

• Is using now existing DOM, so Angular generates the DOM, not the plugin.

overlayscrollbars-ngx@v0.1.1

Improvements:

• overlayscrollbars-ngx has now AoT compilation support.

OverlayScrollbars Version 1.9.1

Bugfixes:

• Fixed a bug where the plugin didn't update correctly if you changed interleaved options twice in a row to the same value

Improvements:

• created build script (build.js file)
• The react, vue and angular components are finally out, you can install them via npm or you can find them in the packages folder:

npm install overlayscrollbars-react

npm install overlayscrollbars-vue

npm install overlayscrollbars-ngx

OverlayScrollbars Version 1.9.0

Bugfixes:

• Fixed a bug where unexpected scroll jumps happened after you changed a option.
• Fixed a bug where a min-width change wasn't detected if width is auto
• Fixed a bug where the update function didn't update a textarea properly, when only its value changed and due to that its size.

Features:

• A new global method OverlayScrollbars.valid which checks whether a passed object is a non-destroyed OverlayScrollbars instance. You can read more about it here.

Improvements:

• The readme has now a TypeScript section.

OverlayScrollbars Version 1.8.0

Bugfixes:

• Fixed #122
• Fixed #120 and #119 with autoUpdate : true set.
• Fixed a bug where the update() method didn't undo the sleep() method like it should.

Features:

• The getState() methods returned object contains now a new property called destroyed which indicates that the instance has been destroyed.

Improvements:

• Changed the management of passive event listeners: touch events which call prefentDefault() are now added with passive : false, all other events which should be passive and don't call prefentDefault() are added with passive : true. Fixed #124 with this change.
• Preparation for framework wrappers such as react, vue and angular: the option() method will now only cause a call to the update() method if at least one option has been truly changed.

Internal Changes:

• Cleaner handling of the internal update() method.
• Preparation for DOM-tests.

OverlayScrollbars Version 1.7.3

Bugfixes:

• Fixed #120 - the status of the DOM / MutationObservers is now synchronized if you call the scroll or update function.
• Fixed #119 - the used MutationObserver listens now to the open attribute.
• Fixed a bug where you couldn't resize the host element when its size was 0 previously.
• Fixed a IE8 bug where the plugin didn't work correctly.

OverlayScrollbars Version 1.7.2

Bugfixes:

• Fixed a bug where width: auto elements had incorrect width if paddingAbsolute was true.

Improvements:

• OverlayScrollbars has better perfomance on Firefox now because it utilizes the new scrollbar-width CSS Property.
• Improved perfomance on all browsers which are using natively overlaid scrollbars (mobile, OS-X etc.).
• Changes to the textarea size measuring process, which results also in better performance if plugin is initialized on textarea elements.

Please make sure you use the latest CSS file, else you won't gain the performance improvements on Firefox!

OverlayScrollbars Version 1.7.1

• Fixed #110

OverlayScrollbars Version 1.7.0

Bugfixes:

• Fixed #98
• Fixed #94 - The eval() call in the scroll method is now only needed if you pass a calculation or a unit string. Coordinates like 500, "500px", "+=500", "+=500px" are now executed without eval().
  Advanced coordinates with other units than px like "50%", "1vw", 1vh or whole calculation strings like "100px - 5%", "50% - 10px + 1vh" still needs the eval().
• Fixed #102 Scaled host-elements are no longer a problem. You can test this with the new scaling demo!
• Fixed a bug where the textarea-size was calculated incorrectly when padding was 0.
• Fixed a bug which caused the overflow-amount to be incorrect on auto-sized elements.

Features:

• A new option scrollbars.snapHandle was added which helps you to control how the scrollbar-handle behaves if you use CSS Snap Scrolling. Read more about it in the documentation
• The scroll() methods returned object now has a new property called snappedHandleOffset. This is a object which represents the current handle-offset as if it was snapped with CSS Snap Scrolling, the normal handleOffset represents the current non snapped handle-offset. You can read more in the documentation which is up to date.

Improvements:

• CSS Snap Scrolling has now deeper support: The handle dragging is now smooth (controlled with the new option scrollbars.snapHandle) and the jump-back if you let go midway has now a transition.
• If you set a handle-max-size and the overflow is way to small, the resulting jump-back if you let go midway has now a transition.
• If you drag the handle the next calculated scroll-position is now rounded instead of floored which results in better user-experience.
• Click scrolling is now more precise.

Changes:

• The since v1.6.0 deprecated object which the .scroll()-method returns is now removed. You can read more details in the documentation. I've removed it to reduce the code size.

Internal Changes:

• Summarized certain code-parts where the same action was perfomred for each axis separately which reduced the code size.