Closed TS-Tobias closed 1 year ago
The comment in there comes from a misunderstanding of my own - I had been under the impression that, since Chrome uses -webkit-
vendor flags, it was "Webkit based." (D'oh!) Of course, this hasn't been true for almost 10 years now. Where I say "webkit-based" there, I really mean "Chrome."
I'll have to do a little more research, but I vaguely remember that the reason I included that default styling was to get Chrome to behave like Firefox. (Firefox offers much less scrollbar customizability than Chrome does, so it ends up being the least common denominator.) I think the overflow logic on Firefox is actually more complicated than I realized at the time, though, so either way, it needs a revisit.
Of course, this is all based on vague memories of something I thought about a couple years ago, so I could be talking straight out of my behind.
Fixed in version 3.
Fixed in version 3.
Hello! Is version 3 the current stable version?
Sure is.
It is not true that
overflow-overlay
only affects Webkit-based web browsers (I observed this behavior in MS Edge (Chromium)). https://github.com/adoxography/tailwind-scrollbar/blob/a28e46b8c257b7ddc43abb9a03f2a56c18bcd7eb/src/utilities.js#L32Would it be possible to remove
overflow-overlay
from thescrollbar
andscrollbar-thin
class and instead create an additional classscrollbar-hover
to enable this behavior for chromium-based browsers?overflow: overlay
is deprecated anyway and will eventually stop working (docs). To prevent the behavior ofscrollbar
andscrollbar-thin
from changing in the future, it makes more sense to extract theoverflow: overlay
property into a separate class and give users the choice if they want to use it or not.Originally posted by @TS-Tobias in https://github.com/adoxography/tailwind-scrollbar/issues/12#issuecomment-1342331073