-
Notifications
You must be signed in to change notification settings - Fork 37
Accidentally changing rating while scrolling on mobile #852
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
Comments
Hi @LeonNamowitz, thank you for bringing this up. This has happened to me in the past, luckily I usually see the popup saying 'Saved' and I realise what has happened. Just been looking at this on the beta site, I think a possible solution could be cancelling the rating change if the page scrolls too far down from where it was when initially pressed down. Will have to play around with it though when I have the time, if anyone else has any better ideas, I would be happy to hear them! This one doesn't sound that great, but if it works for now, it'll hopefully be better than the current situation. |
Happend too me a couple of times too and its really annoying if you don't notice it instantly. I would take another approach. I would just show one star with the rating next to it, for example like imdb does. if there i no rating yet just for a gray star for example. |
Yeah I almost agree with @Seyloria that it should ideally just be 2 clicks or touches to set a rating. 1 additional click is totally fine and it would avoid the issue entirely. It's just a UI question I think. I like the current look and for example some sort of confirmation dialog could also work. |
Not sure if this is only me but while using the site on mobile on multiple occasions now I accidentally changed the rating of something while just scrolling down to the activity field because my finger happens to touch the rating area at some point.
Sometimes I don't notice this (there is no feedback or anything) until way later or worse not at all.
I'm not even sure how we could improve this but maybe someone else has an idea?
The text was updated successfully, but these errors were encountered: