-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
fix[Closes #427]: Only show "Retry connection" button after a failure and skip over connection test page when navigating backwards #446
base: main
Are you sure you want to change the base?
Conversation
…n messages on the connection check page
I'm open to suggestions on how to skip over the connection test page only when navigating backwards. From my read of the code, it doesn't seem like pages currently have knowledge of which page comes before or after them, simply that they must navigate to the next ID. This is problematic for this case unless we decide to only perform the connection check once, which may be undesirable. |
Screencast.From.2024-12-01.23-56-34.mp4Behaves as expected now. |
I think only automatically skipping forward once is acceptable here. |
I'm not sure I understand what you mean. The original issue states that, since the connection test page navigates forwards automatically, it makes it difficult to return to the "language" or "welcome" pages when using the back button to navigate as you will be automatically booted back to the next page. This is more about skipping over the connection test page when navigating backwards (but not forwards). |
Yes, I would suggest the installer skips to the next page after the check is complete but then remembers that and doesn't skip a second time, no matter what direction the user is going. (That might require a "check successful" text though, to not be confusing) |
An interesting solution. This would definitely resolve the navigation issue, although I feel like at this point, the page could simply be hidden from navigation as it is no longer useful, but that might be harder to implement than your more straightforward solution and would involve a skipping mechanism. |
Work to do: