I’m using this firefox extension to generate passwords. This works fine but I guess it doesn’t trigger whatever event discourse is looking for on the form field, so the register button stays disabled until I change something else in the form.
AI-generated summary
Users are experiencing issues with the signup button remaining disabled after generating passwords using certain extensions, such as PasswordMaker and ChromeIPass. However, neil notes that 1Password seems to work correctly. gerhard suggests this may not be a Discourse issue, but ThiefMaster proposes a potential workaround by checking for a password value at regular intervals. As a temporary solution, users can try adding and removing a space to the end of the password to signify intent to the browser, as suggested by riking and confirmed by JSey.
1개의 좋아요
I use 1password to generate and fill passwords, and it’s triggering the correct events in Firefox on Discourse sites. That addon will need to do the same. Maybe Lastpass works too.
1개의 좋아요
It’s a common problem with such extensions. chromelPass has the same issue.
Correct me if I’m wrong, but I don’t think this can be fixed in Discourse…
The standard workaround is to add and remove a space to the end of the password. This signifies intent to the browser that you want the page to be able to see the value.
2개의 좋아요
That’s what I do - I have the very same problem using 1password.
Depends on how pretty the fix needs to be. Checking for the password field having a value in a a 250ms interval once all other fields have one wouldn’t be extremely pretty but not that bad either..