-
Notifications
You must be signed in to change notification settings - Fork 25
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
Remove "cannot go in the direction you want me to walk" option from Jump button #3676
Comments
Sounds good! |
@aslassi777 here's your next task! |
5 tasks
thanks! checking it out |
Sounds good @misaugstad! I see the page ModalSkip.js. I will make the changes this week and push when ready, and I will try to clean up/document the code a litte! |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Brief description of problem/feature
For the past few months, I've been periodically looking at streets where users have been skipping the street because they clicked the jump button and said that they couldn't walk in that direction, hoping to remove any streets that we don't actually have imagery for. But what I've found is that in almost all cases, users could have successfully made it down the street if they clicked the "Stuck" button instead; the issue is just that GSV doesn't have a direct link between two panos for some reason. This means that people are skipping streets that they could normally be auditing, and I'm wasting my time looking at those!
At this point, I think that we should just remove that option from the Jump button. We can change the dialog to instead just tell users that if it seems like they can't move forward, that they should click the "Stuck" button. And the modal just becomes essentially a "confirm you want to jump" dialog. That way users can still choose to jump to a new part of the neighborhood if they want, but we get to move users towards the Stuck button if the issues is that they're stuck.
Let's also move the Stuck button above the Jump button!
A quick draft of some text / list of changes:
There's plenty that we should do to redesign this ugly dialog that will look even worse after these changes, but it's not used super frequently, and that's outside the scope of this change that should be pretty quick!
The text was updated successfully, but these errors were encountered: