-
-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] Remove custom scrollbar styling #540
Comments
To disable the custom scrollbar, simply remove these few lines. You probably want to set the color-scheme as well so the native scroll bar fits the dark mode. DoIt/assets/css/_core/_base.scss Lines 18 to 30 in 8e778b4
Chrome Firefox does not support this customization anyway. |
@HEIGE-PCloud thanks for the quick response! Sorry, I should have stated my env:
And yes, you're right, the
And I guess the auto hide behaviour is only present on macOS. Same with the thickness, it's thinner on my OS, when using native styling, than what the customisation sets. Yes, I found the CSS responsible for it, but I didn't want to deviate from the upstream (this repo) and remove styling there. Are you aware of another way of achieving the same result without making a fork of the theme and add my own commits on top? I've just started hugo, so maybe there's something I don't know? I know that you can override and add custom CSS by adding the Ultimately, this is a very small thing I guess 😆 And it would only make a diff to a small amount of users. |
Set $custom-scrollbar: false; in your_site/assets/css/_override.scss can disable the custom scrollbar. |
@HEIGE-PCloud that was fast! Thanks a lot! |
Describe the feature you want 描述你的功能需求
I recommend removing the custom scrollbar styling for a couple of reasons:
Or maybe make it so it's easy to disable the theme behaviour and use the native one (maybe via a scss var or something). If this is something that would be considered, I could make a PR.
Btw, I really like the theme!
Useful reference 有价值的参考
No response
The text was updated successfully, but these errors were encountered: