OverlayScrollbars Version 2.0.0

Read the details about this release in the corresponding changelogs:

• overlayscrollbars v2.0.0
• overlayscrollbars-react v0.4.0
• overlayscrollbars-vue v0.4.0
• overlayscrollbars-ngx v0.4.0
• overlayscrollbars-svelte v0.4.0
• overlayscrollbars-solid v0.4.0

OverlayScrollbars Version 1.13.3

Improvements:

• #452 change appear animation detection from z-index to cursor.
• #447 only call image callback when the plugin isn't destroyed.

OverlayScrollbars Version 1.13.2

Improvements:

• #434 Fixed onInitializationWithdrawn callback
• #377 Fixed HTMLImageElement Memory Leak

React:

• Added React 18 support

Vue:

• Added Vue3 support

OverlayScrollbars Version 1.13.1

Improvements:

• #256 Fixed z-index of .os-padding.
• #263 Fixed passive event-listeners on touch events

Angular:

• #210 updated peerDependency to >=7.0.0 to remove warnings for angular versions higher than 7
• #281 changed OverlayScrollbarsComponent properties from private to public to make it work with angularCompilerOptions.strictInputAccessModifiers

OverlayScrollbars Version 1.13.0

Improvements:

• #251 If you drag the scrollbar handle the click event won't be propagated to the body to be closer to the native behavior.
• #240 The .os-padding element has now default z-index.
• #238 Clickscrolling amount & speed adjusts now to the scrollbar-handle size to be more accurate.
• #226 The RTL(right to left) style won't be applied to the body element anymore to be closer to the native behavior.

OverlayScrollbars Version 1.12.0

Improvements:

• Implemented #197 - max-content is now used to detect the possible size if width is not fixed. (only if supported by the browser else the old algo. is used)
• Updated all wrapper versions to better support frontend frameworks. (#193)
• Removed useless touchevents from the host element (#195)
• GUI Tests

Features:

• A new option called updateOnLoad with which you can control on which elements / selectors OverlayScrollbars shall update automatically after the emit of a load event. Per default the value is set to ["img"] so the plugin will updated after any img emits a load event. You can set it to null to disable this auto updating entierly or add your own selectors to update only on special img elements or on for example loaded iframes. (#183)

Bugfixes:

• Fixed #190 - Removed the browser property inside of all package.json files (revert #166)

Deprecated:

• The cssCalc property inside the object which gets returned from the globals() is now deprecated and will be removed in future versions.

OverlayScrollbars Version 1.11.0

Improvements:

• Changed RTL behavior detection to support the Chromium web interoperability effort #187
• Implemented a way to intuitively set the tabindex attribute of the viewport element #153
• Changed restrictedMeasuring workaround (works via CSS now). Fixes #191
• Removed unnecessary CSS

Bugfixes:

• If ResizeObserver is supported, it now detects changes in padding in Chrome again.

Please make sure you use the latest CSS file, else version 1.11.0 won't work!

OverlayScrollbars Version 1.10.3

Improvements:

• The cache of the scroll infos which can be get by the scroll method is now updated immediately after you use the scroll method to change the position.
• Fixed #178.

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.