You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Frontend checks, if there is at least one letter in the field. So for example '123a' will be acceptable. But if there are only digits in the field, proceed buttons ('continue to payment' and 'go to review order') become inactive/grayed. However, no validation message is displayed, so user have no idea, why he cannot proceed. He may not even be aware that he made a mistake somewhere in the form.
Expected behavior
Front behaviour should reflect backend validation. If input is unacceptable (like in this case) - proper validation message should appear.
Repository
All (demo, next, test)
Can you handle fixing this bug by yourself?
YES
NO
Which Release Cycle state this refers to? Info for developer.
Pick one option.
This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.
Additional information
The text was updated successfully, but these errors were encountered:
Related issue:
#2653
Steps to reproduce the issue
Current behavior
Frontend checks, if there is at least one letter in the field. So for example '123a' will be acceptable. But if there are only digits in the field, proceed buttons ('continue to payment' and 'go to review order') become inactive/grayed. However, no validation message is displayed, so user have no idea, why he cannot proceed. He may not even be aware that he made a mistake somewhere in the form.
Expected behavior
Front behaviour should reflect backend validation. If input is unacceptable (like in this case) - proper validation message should appear.
Repository
All (demo, next, test)
Can you handle fixing this bug by yourself?
Which Release Cycle state this refers to? Info for developer.
Pick one option.
develop
branch and create Pull Request2. Feature / Improvement
back todevelop
.release
branch and create Pull Request3. Stabilisation fix
back torelease
.hotfix
ormaster
branch and create Pull Request4. Hotfix
back tohotfix
.Additional information
The text was updated successfully, but these errors were encountered: