mirror of
https://github.com/anonaddy/anonaddy.git
synced 2026-04-25 22:25:55 +03:00
[GH-ISSUE #645] Re-entering password required after incorrect CAPTCHA on sign-up #1026
Labels
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/anonaddy#1026
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @maninthemiddle01 on GitHub (May 27, 2024).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/645
When I tried to sign up and solved the CAPTCHA incorrectly, I am prompted to solve the CAPTCHA again. However, in this process, the password input field is cleared, requiring the user to retype their password.
Expected Behavior:
When a user inputs an incorrect CAPTCHA during the sign-up process, the password input field should not be cleared and retain the previously entered password.
Steps to reproduce:
Potential Solution:
Retain the entered password in the input field even after an incorrect CAPTCHA submission, so the user only needs to correct the CAPTCHA and not retype their password.
@willbrowningme commented on GitHub (May 27, 2024):
The password is not kept after a page refresh as you describe above by design. This is in order to keep sensitive data out of the session.
https://laravel.com/docs/11.x/requests#old-input