https://bugs.kde.org/show_bug.cgi?id=412569
--- Comment #2 from Ricky Tigg <ricky.t...@gmail.com> --- Hey. You all interpreted correctly. I used Fedora, Gnone. Once entering a password in only one field, be it the first or second, invoking OK starts an endless process. At this state, 1. Attempting to enter into the confirmation field a password won't be operational; 2. OK button wss greyed out, while Cancel button alone was available. Some observations: – OK button has been in my tests available for being invoked right from the beginning of the apparition of window illustrated by kleopatra_3.1.4_failed_password_setting_1.png while no passwords had yet been entered into any fields. – The second field –the one aimed for password confirmation– was opened to receive some content even while the first field –the one aimed to enter a reference password– had been left blank. Yet during that operation, OK button remained available. Those reflections came to me: – OK button could be greyed out right from the beginning until both fuels have been supplied with some content which then make it at last available for beeing invoked. – The second field could be closed, eventually adding a greyed-out background to it in order to make its state explicit, until a password has been entered into the first field and user has switched to the second field. – Once both fields have been supplied with content, invoking OK button would process informations contained within these fields then check that they match each other. In case they don't, a typical message related to the situation would be exhibited, such as "Passwords do not match each other.", but without the need to lead to a failure. -- You are receiving this mail because: You are watching all bug changes.
