Simplify Captain setup into focused connection views - #174
Merged
Merged
Conversation
Signed-off-by: Sridhar Bala <sridharkalaibala@gmail.com>
…setup Signed-off-by: Sridhar Bala <sridharkalaibala@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Setup mixed address entry, discovery, phone approval, and backup connection settings on one page. Captain now keeps one task visible at a time: enter an address and continue to staff sign-in, or open Wi-Fi discovery, pairing code, or browser approval in a separate view. Continue always uses the entered address. First setup and Change server use the same flow.
Back preserves the typed address and cancels pending discovery. Late discovery or address-probe responses cannot navigate after the user leaves. Failed browser approval returns to the starting view for a fresh attempt. Backup addresses have a dedicated view, and setup retains all 30 interface languages.
Validation: production build and translation audit; 572 unit checks; 474-case browser regression run (467 passed; seven old-interface assertions updated and covered by an 18/18 passing rerun). Phone, tablet, and Tamil settings screenshots reviewed. Physical Azure handset approval remains a device verification step.