diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2020-11-28 10:39:30 +0100 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2020-11-28 10:39:32 +0100 |
| commit | 854b36cfa2ef017567dcf1e7d0304107a8700f2b (patch) | |
| tree | b08fde29ba835a01e0a598ce3b1acb3b7186434b /test | |
| parent | 1ae5758981de15a8c0713bfdae216bf91d607c57 (diff) | |
| parent | 8008ef770f3d0b14d03e22371314500373732143 (diff) | |
| download | bitcoin-854b36cfa2ef017567dcf1e7d0304107a8700f2b.tar.xz | |
Merge bitcoin-core/gui#138: unlock encrypted wallet "OK" button bugfix
8008ef770f3d0b14d03e22371314500373732143 qt: unlock wallet "OK" button bugfix (Michael Dietz)
Pull request description:
When trying to send a transaction from an encrypted wallet, the ask
passphrase dialog would not allow the user to click the "OK" button
and proceed. Therefore it was impossible to send a transaction
through the gui. It was not enabling the "OK" button after the
passphrase was entered by the user, because it was using the same
form validation logic as the "Change passphrase" flow.
I reported this in a comment in https://github.com/bitcoin-core/gui/issues/136. But then I realized this seems to be a flat out bug.
ACKs for top commit:
MarcoFalke:
review ACK 8008ef770f3d0b14d03e22371314500373732143
hebasto:
ACK 8008ef770f3d0b14d03e22371314500373732143, I have reviewed the code and it looks OK, I agree it can be merged.
Tree-SHA512: cc09b34c7f3aea09729e1c7ccccff05dc11fec56fee2ad369f2d862979572b1edd8b7e738ffe6e91d35d071b819b0c3e0f5d48bf5e27427a80af4a28893f8aaf
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions