Malte Wessel
Malte Wessel
checking scrollbar width on every `handleWindowResize` would lead to a huge performance drop and since this is an edge case I'm not really happy with this approach
I will think of a solution for this
Hey guys, sorry responding so late, I will try to work through all the issues and PRs in the next couple of days/weeks!
Hey guys, sorry for the trouble. I'm open for contributors. Would be great if some experienced developer could take over? Any suggestions?
Hey, thanks for your efforts! The library was actually meant to not use the custom scrollbars on mobile, since devices have their own style, and that should be the preferred...
You'll need to make the Scrollbars' child components wider than the Scrollbars component itself. This can be done with a fixed width on the child components.
Maybe you could force the tabs to overflow with the help of css. If you got `inline-block` elements you could set `white-space: nowrap;` on the tabs container element, to ensure...
Yes, thanks for mentioning. You need to ensure that a **rerender** is triggered from the `Scrollbars` component down to its children.
You need to ensure that not just the children are rerendered but also the `Scrollbars` component.
@amirmohsen yes, actually this would be cool. But since the [Resize Observer](https://wicg.github.io/ResizeObserver) API is in an early stage, I don't want to ship this library with the polyfill. The polyfill...