| Summary: | Password field not re-enabled immediately after it was disabled by entering a username with an incorrect server URI | ||
|---|---|---|---|
| Product: | [Applications] NeoChat | Reporter: | Nate Graham <nate> |
| Component: | General | Assignee: | Tobias Fella <fella> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | carl |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
This was fixed in the recent rework of the login flow |
STEPS TO REPRODUCE 1. Click Switch User > Add Account 2. As the username, give it "@[username]:opendesktop.org" 3. Enter password OBSERVED RESULT A PassiveNotification is shown in the main window (not the login window) saying something like "the current homeserver is not good". When I figured out the correct username ("@[username]:chat.opendesktop.org") and tried again the password field was still disabled. It was only re-enabled after NeoChat sent another PassiveNotification informing that a network request timed out a minute or so later. EXPECTED RESULT When this happens, the password field is re-enabled immediately