-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Input values are not cleared #17
Comments
Are you needing to create a new instance for any other reason than just to clear the input fields? If not, I think we should look at a different approach/fix. Creating a new instance every time seems unnecessary. |
No, ideally the lock would clear the input values once authentication is successful. |
I've submitted an issue for this in the Lock repo: auth0/lock#795 Stay tuned there for a change there. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you have not received a response for our team (apologies for the delay) and this is still a blocker, please reply with additional information or just a ping. Thank you for your contribution! 🙇♂️ |
Hi,
This issue is specific to popup mode login, as there is no redirection, the auth0 lock instance will remain in browser memory. Due to that nuance, when user logs out, and opens the log-in window again (rememberLastLogin disabled), the input fields in the lock remain from previous login.
I decided that angular-lock would be more fitting repo for this issue, as with the original lock I could create new instance of the lock every time the button is pressed, however with angular, there is only single lock instance created with app initialization.
Video explains better: https://youtu.be/frPcOG40C-s
Regards,
ozooner
The text was updated successfully, but these errors were encountered: