-
Notifications
You must be signed in to change notification settings - Fork 271
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
Create new account page does not detect filled out fields after translation - Amplify Authenticator UI Component #247
Comments
Problem remains. Test URL from @liamaws have been changed to https://master.dw8p5s05jola3.amplifyapp.com |
Quick question – how is the translation being changed? Is there a language icon in a nav-bar that an end-user can change at any point in time? |
Yes there was button at the top of page that a user can click at any time to change the language of the page. But the issue isn't specific to translation so that is kind of misleading. The issue is that fields will remain filled out in the UI but not actually be considered filled out. Basically the second scenario where no translation is involved is also a problem. |
We'll need to send a PR to Amplify JS to support this scenario: As for this issue:
This bug should be fixed in losing-values.mp4 |
Hello all, sorry for the tardiness on this issue. This should be resolved in our latest |
Describe the bug
After filling out the create account page of the Amplify Authenticator UI Component and then changing the translation, the fields remain filled out on the UI but are not detected when clicking the create account button.
To Reproduce
Steps to reproduce the behavior:
I would like to point out that this problem is not specific to using a translation.
It can also be reproduced by doing the following
Expected behavior
An account will be created with the information that has been filled out and is present on the UI.
Code Snippet
Screenshots
![image](https://user-images.githubusercontent.com/67014943/89562640-45b38980-d7e8-11ea-9c5d-47a3b9da9677.png)
The text was updated successfully, but these errors were encountered: