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

[Minor] Back button on first page leads to stuck Dice page #14

Open
lkhwa opened this issue Jun 5, 2017 · 3 comments
Open

[Minor] Back button on first page leads to stuck Dice page #14

lkhwa opened this issue Jun 5, 2017 · 3 comments
Labels

Comments

@lkhwa
Copy link

lkhwa commented Jun 5, 2017

Steps to reproduce:

  1. Navigate to Level app
  2. Select any Class (e.g. Fighter)
  3. Select any Level (e.g. Level 1)
  4. Click the Back button immediately, as follows:

screen shot 2017-06-04 at 11 37 56 pm

5. Step 4 has led to the Dice page, with both Back and Next buttons greyed out. Hitting refresh (upper right corner) still keeps you on the same page.

screen shot 2017-06-04 at 11 38 57 pm

Currently, the only way to exit is to press the back button manually on the browser, which doesn't seem ideal. You could probably disallow the Back button on step 4, or have clicking on the "Level" logo redirect to the home page :)

@isabelgiang
Copy link
Owner

Hi, thanks for your feedback! Could you provide more details on how you reached this issue? We're currently unable to replicate it.

@lkhwa
Copy link
Author

lkhwa commented Jun 5, 2017

Sure! Hope this screencapture helps: https://im3.ezgif.com/tmp/ezgif-3-3016289cf8.gif

@isabelgiang
Copy link
Owner

isabelgiang commented Jun 7, 2017

This issue occurs only with the Safari browser, which is why we were unable to replicate the error as devices with Windows were primarily used to test the application. Specifically, this seems to be an issue with how Safari handles the React DOM root node.

Due to our limited understanding of the Safari development environment, we were unable to isolate the specific cause of this issue despite spending several hours attempting to debug it.

Additionally, this does not impact Safari users' ability to utilize our application's main functionality.
For these reasons, we will not be fixing this issue for our first patch.

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

No branches or pull requests

2 participants