You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The carousel used on the https://app.opensauced.pizza/explore page does not implement mouse-scroll natively, and nor do the carousels on the Explore page. Instead, it implements drag-to-scroll, which requires a Desktop user, especially on Windows/Linux, to have to double click and then scroll to the slide OR click the left and right side buttons.
These are all unnecessary and unintuitive extra steps, especially when simple side scrolling with the mouse can be implemented. Here is an example of that.
It feels more intuitive, is easier for mobility impaired users on device models with limited trackpad capabilities, and more precise as well.
Thanks for the issue, our team will look into it as soon as possible! If you would like to work on this issue, please wait for us to decide if it's ready. The issue will be ready to work on once we remove the "needs triage" label.
To claim an issue that does not have the "needs triage" label, please leave a comment that says ".take". If you have any questions, please comment on this issue.
For full info on how to contribute, please check out our contributors guide.
Describe the bug
The carousel used on the https://app.opensauced.pizza/explore page does not implement mouse-scroll natively, and nor do the carousels on the Explore page. Instead, it implements drag-to-scroll, which requires a Desktop user, especially on Windows/Linux, to have to double click and then scroll to the slide OR click the left and right side buttons.
These are all unnecessary and unintuitive extra steps, especially when simple side scrolling with the mouse can be implemented. Here is an example of that.
It feels more intuitive, is easier for mobility impaired users on device models with limited trackpad capabilities, and more precise as well.
Steps to reproduce
The text was updated successfully, but these errors were encountered: