Nag-bar and dialog for Passwordless Users to provide password

[lampholder]

The details of the new guest experience for Riot are on the project plan: element-hq/riot-meta#59

Users who have provided a username and completed a CAPTCHA should be prompted to complete their registration to avoid losing access to said username.

This should use the existing 'You are Rioting as a guest' top notification bar, and should include a link to the mechanism to complete registration.

[lampholder]

@ara4n @AmandineLP we need some wording for the nag box.

We probably want to go for something like one of these four (steadily increasing in level of alarm):

1. Please click here to complete registration of your Riot account.
2. To log in on other devices, please complete registration by setting a password for this account.
3. To claim @GreatName:matrix.org complete registration by setting a password.
4. Without completing registration you risk losing @GreatName:matrix.org forever! Set your password now!

[lampholder]

The current nag bar features links to log in or to register.

We might want to consider a button here instead since buttons are more actiony:

[AmandineLP]

M & I suggest:

To be able to return to your account, you need to set a password. [............]

[lampholder]

Is that the password field in the nag bar itself?

[lukebarnard1]

Is that the password field in the nag bar itself?

Conclusion was that, no it's the "Set Password" button.

[lampholder]

The current registration password set UX has some issues:

• password criteria (minimum length == 6) is not written and has to be discovered by typing
• if there is anything wrong with you password (too short or mismatched) it just wears a red border and shakes itself side to side
• the field names are only there as placeholder text (so they can be completely hidden by malfunctioning form auto-completes)

The strickenthrough issues above were experienced by password feedback being below the fold on my macbook air :\ #3893

To move forward, I suggest we:

1. Implement a naive impl of the password by dropping the password set components from the registration page into here
2. Prioritise reworking our password set UX as a separate task.

Thoughts?

[lukebarnard1]

@lampholder this feels like the wrong place for that. This issue is for the nag bar and the new dialog for changing passwords.

[lukebarnard1]

^ Initial simple implementation of the dialog has now been merged.