-
Notifications
You must be signed in to change notification settings - Fork 16
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
Fixes needed for problems with navigation and using the game. #430
Comments
Do you still want to keep the prompt for "LEFT CLICK TO DRAW"?
What specifically does "edge wrapping" refer to?
Does this include large-screen mobile devices like iPads? |
PR: #436
Resolved.
Everything has been resolved except for
I need to wait for a response to the question I commented on above before starting the processing.
Unable to reproduce, need help from @Keith-CY or the testing department. |
@WhiteMinds My apologies for not responding sooner. I did not see the message until now.
Keep on Chrome desktop only.
It means when the cells move off the screen they appear on the opposite side. eg: If it moves off the right side of the screen, you see it appear on the left side. If it goes off the bottom, it appears at the top.
Yes, the buttons are too hard to press on all touch screen devices so remove them as a temporary fix. |
After trying the newest deployed version, I have a few more recommendations:
Notes: Pressing tab has occasionally caused the page to scroll halfway between two sections, effectively breaking it and forcing the user to refresh. However, this seems to be very rare so I think it can be skipped for the time being. |
@PainterPuppets could you do me a favor to handle this issue |
Some users have had issues with page navigation and with the game. In the interest of giving the best user experience while realizing we have limited resources available, we need to prioritize functionality over cosmetics and nice-to-have features.
Per discussion with Matt, I am submitting the following recommendations:
A full log of all issues can be found here, which contains more details about anything mentioned above.
The text was updated successfully, but these errors were encountered: