Skip to content
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

cubari: Custom scrollbar uses move cursor instead of default (pointer) cursor #80

Open
ErikHumphrey opened this issue Dec 31, 2020 · 2 comments

Comments

@ErikHumphrey
Copy link

The custom scrollbar should use the pointer cursor rather than the move (grabber) cursor. It may also be possible to use CSS to change the look of the scrollbar rather than inventing a custom one, but I would imagine there is some functional reason for using a custom one here other than looks.

Cursor before:

image

Cursor after:

image

It's better UX to have scrollbar replacements retain the same pointer as other scrollbars; else, it ruins the illusion and feels bad.

@ErikHumphrey ErikHumphrey changed the title Custom scrollbar uses move cursor instead of default (pointer) cursor Ccubari: Custom scrollbar uses move cursor instead of default (pointer) cursor Dec 31, 2020
@ErikHumphrey ErikHumphrey changed the title Ccubari: Custom scrollbar uses move cursor instead of default (pointer) cursor cubari: Custom scrollbar uses move cursor instead of default (pointer) cursor Dec 31, 2020
@Algoinde
Copy link
Member

The scrollbar is implemented exactly as you suggested, it's not a non-native implementation. The problem lies in the fact that the whole container is cursor-pointer'ed. I can put this on my list to fix if this annoys you.

@ErikHumphrey
Copy link
Author

Ah; I wasn't too sure and should have checked the code first. I had a feeling that might be the case, but I didn't know that the WebKit scrollbar could overlay & inherit from page contents even on systems where the default puts the browser scrollbar beside the content rather than over it.

Yes, please fix it when you have the chance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants