# Signup button remains disabled when inserting generated password
**URL:** https://meta.discourse.org/t/signup-button-remains-disabled-when-inserting-generated-password/33357
**Category:** Bug
**Created:** [16 Setembro , 2015 15:06 UTC](https://meta.discourse.org/t/signup-button-remains-disabled-when-inserting-generated-password/33357 "2015-09-16T15:06:41Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@ThiefMaster](https://meta.discourse.org/u/ThiefMaster)
#### Post date: [16 Setembro , 2015 15:06 UTC](https://meta.discourse.org/t/signup-button-remains-disabled-when-inserting-generated-password/33357/1 "2015-09-16T15:06:41Z")
I’m using [this firefox extension](https://addons.mozilla.org/en-US/firefox/addon/passwordmaker/) 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.
---
### Author:  [@neil](https://meta.discourse.org/u/neil)
#### Post date: [16 Setembro , 2015 19:57 UTC](https://meta.discourse.org/t/signup-button-remains-disabled-when-inserting-generated-password/33357/2 "2015-09-16T19:57:38Z")
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.
---
### Author:  [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [16 Setembro , 2015 20:13 UTC](https://meta.discourse.org/t/signup-button-remains-disabled-when-inserting-generated-password/33357/3 "2015-09-16T20:13:10Z")
It’s a common problem with such extensions. [chromelPass](https://chrome.google.com/webstore/detail/chromeipass/ompiailgknfdndiefoaoiligalphfdae) has the [same issue](https://github.com/pfn/passifox/issues/351).
Correct me if I’m wrong, but I don’t think this can be fixed in Discourse…
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [16 Setembro , 2015 23:49 UTC](https://meta.discourse.org/t/signup-button-remains-disabled-when-inserting-generated-password/33357/4 "2015-09-16T23:49:38Z")
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.
---
### Author:  [@JSey](https://meta.discourse.org/u/JSey)
#### Post date: [17 Setembro , 2015 17:40 UTC](https://meta.discourse.org/t/signup-button-remains-disabled-when-inserting-generated-password/33357/5 "2015-09-17T17:40:20Z")
That’s what I do - I have the very same problem using 1password.
---
### Author:  [@ThiefMaster](https://meta.discourse.org/u/ThiefMaster)
#### Post date: [17 Setembro , 2015 23:14 UTC](https://meta.discourse.org/t/signup-button-remains-disabled-when-inserting-generated-password/33357/6 "2015-09-17T23:14:42Z")
> [@gerhard](#):
>
> Correct me if I’m wrong, but I don’t think this can be fixed in Discourse…
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..