Chrome password generation when registering doesn't work / Riot doesn't work with password managers

[slikts]

When using the feature in Chrome to generate a password, the first password field in the registration form gets cleared so it's not possible to register.

Web client, Chrome 64

[lukebarnard1]

@slikts do you happen to know which version of the app you were running? (Was it https://riot.im/app?)

[slikts]

https://riot.im/app/#/register
How the feature is accessed:

What happens when I press "Use a strong password generated by Chrome":

This is a significant oversight since using a password manager is more secure than manually remembering passwords.

[lampholder]

Is the experimental Chrome password generator enabled via chrome://flags?

The registration page seems to play nicely with other password managers (it works fine with LastPass for example).

The Chrome generator certainly does fail to populate the first password box, though at this stage that seems almost as likely to be a bug in the generator as it is an oversight in our registration UX. Our registration form is a simple HTML form with two HTML <input>s of type 'password', so it's not unreasonable to expect that to work properly.

As I understand it, there's no agreed recommended password-manager-compatibility spec - if you are aware of such a spec then please let me know (I'd love to implement it as I am hugely in favour of use of password managers).

[slikts]

It's an old and stable feature and probably behind a flag just to avoid confusing casual users. I've used it extensively for years and this is the first time there's been a problem.

[slikts]

Setting any different name attributes on the input fields solves the issue; simplified test case: https://jsfiddle.net/slikts/vzfLbf3d/5/