Transaction confirmation prompt too big - buttons not clickable #15667

1. 
   bitcoin101ch commented at 2:32 PM on March 26, 2019: none

   Second try - first issue got deleted suddenly...

   When confirming too big transactions, depending on screen resolution with each output the buttons move lower and lower until they are not visible anymore on the screen.

   Additionally randomly after a couple transactions the client starts to repeat its content in the confirmation prompt making even the smalest 1:1 transaction unusable as the buttons are not visible, again. (See screenshot)

   I (A) would expect that the buttons are visible no matter how big the transaction content is (for example by making the content scrollable) and (B) don't understand why the content is repeating suddenly.

   Using Bitcoin Knots 17 but have been directed by the developers that the issue belongs to bitcoin/bitcoin

   

   Windows 10 1920x1080 Intel i7

2. fanquake added the label GUI on Mar 26, 2019
3. 
   MarcoFalke commented at 2:47 PM on March 26, 2019: member

   Does this happen in Bitcoin Core as well?

   Otherwise: https://github.com/bitcoinknots/bitcoin/issues/new

4. MarcoFalke closed this on Mar 26, 2019

   ---

5. 
   bitcoin101ch commented at 3:43 PM on March 26, 2019: none

   Yes also with bitcoin core @MarcoFalke

6. 
   MarcoFalke commented at 4:40 PM on March 26, 2019: member

   Thanks, then please include the version of Bitcoin Core that you are using to reproduce the issue and how to reproduce.

7. sipa deleted a comment on Mar 26, 2019
8. 
   bitcoin101ch commented at 11:07 PM on March 27, 2019: none

   @MarcoFalke Bitcoin Core Version 0.17.1

   Easy to reproduce. Just make a transaction with 20 outputs. Result: The confirmation prompt will be too big for your screen and the buttons are not visible anymore.

9. 
   promag commented at 12:39 AM on March 28, 2019: member

   I think we can improve this while ditching QDialog::exec usages.

10. 
    bitcoin101ch commented at 11:31 AM on March 28, 2019: none

    Status remains closed?

11. 
    promag commented at 11:35 AM on March 28, 2019: member

    I'd reopen and tag 0.19.

12. MarcoFalke reopened this on Mar 28, 2019

    ---

13. MarcoFalke added this to the milestone 0.19.0 on Mar 28, 2019
14. laanwj closed this on Jun 6, 2019

    ---

15. laanwj referenced this in commit 9fccdd4ed4 on Jun 6, 2019
16. sidhujag referenced this in commit 543f000a83 on Jun 6, 2019
17. vijaydasmp referenced this in commit b9c0a56bf3 on Oct 23, 2021
18. vijaydasmp referenced this in commit eb279ef2dd on Oct 26, 2021
19. MarcoFalke locked this on Dec 16, 2021
20. knst referenced this in commit 0afe20e7e3 on Jun 15, 2022
21. knst referenced this in commit 5cd7329252 on Jun 15, 2022
22. knst referenced this in commit a081afd3c1 on Jun 16, 2022

Milestone
0.19.0