Bug 471395 - Password field not re-enabled immediately after it was disabled by entering a username with an incorrect server URI
Summary: Password field not re-enabled immediately after it was disabled by entering a...
Status: RESOLVED FIXED
Alias: None
Product: NeoChat
Classification: Applications
Component: General (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Tobias Fella
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-23 16:59 UTC by Nate Graham
Modified: 2023-11-24 13:45 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nate Graham 2023-06-23 16:59:36 UTC 
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
Comment 1 Tobias Fella 2023-11-24 13:45:47 UTC 
This was fixed in the recent rework of the login flow