We'll consider a fix. Right now the scroll area is implemented via RadixUI, which seems to be very good, but your point is clear. If you have any practical tips/ideas/links to a good, solid, cross-browser scrollarea component - please let me know :)
Just, uh... don't have a custom cross-platform scrollarea? This is a feature the browser provides already.
Your page is perfectly usable by just removing `overflow: hidden scroll;` of div.data-radix-scroll-area-viewport`, and `overflow: hidden;` from .s24.
So you'll probably achieve intended behavior of having a scroll area that works on all browsers by just not using any custom scroll area plugin, but a plain <div> instead.
I don't think I've ever had a good experience with a custom scrollbar. If it behaves any differently from every other scrollbar on my system, it's going to be inferior. And scrollbars work differently from system to system.
What are you trying to achieve beyond the default scrolling behaviour?
Ironic, considering that TFA is judgmental about exactly that:
> This approach to coding is far from extinct. One often finds it in software teams, among some highly regarded – though less valued – members. If you've spent several years in the industry or in Computer Science academia, you surely know this subspecies: the developer that replaces a straightforward loop with a series of auto-resolving promises, capped by a cryptic reducer, then revels in their teammates' bewilderment at the sight of the new code. Hardly the personality that you'd select for a coding legend.
And then the site uses JS to implement a feature that every browser has!
HHad3|3 years ago
Your page is perfectly usable by just removing `overflow: hidden scroll;` of div.data-radix-scroll-area-viewport`, and `overflow: hidden;` from .s24.
So you'll probably achieve intended behavior of having a scroll area that works on all browsers by just not using any custom scroll area plugin, but a plain <div> instead.
oneeyedpigeon|3 years ago
What are you trying to achieve beyond the default scrolling behaviour?
ddevault|3 years ago
cryptonector|3 years ago
> This approach to coding is far from extinct. One often finds it in software teams, among some highly regarded – though less valued – members. If you've spent several years in the industry or in Computer Science academia, you surely know this subspecies: the developer that replaces a straightforward loop with a series of auto-resolving promises, capped by a cryptic reducer, then revels in their teammates' bewilderment at the sight of the new code. Hardly the personality that you'd select for a coding legend.
And then the site uses JS to implement a feature that every browser has!
:)