Skip to content
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

No validation message - digits in city field #3723

Closed
1 of 5 tasks
ArturDivante opened this issue Oct 17, 2019 · 0 comments
Closed
1 of 5 tasks

No validation message - digits in city field #3723

ArturDivante opened this issue Oct 17, 2019 · 0 comments
Assignees
Labels
bug Bug reports P3: Normal Priority mark - normal priority
Milestone

Comments

@ArturDivante
Copy link
Collaborator

ArturDivante commented Oct 17, 2019

Related issue:

#2653

Steps to reproduce the issue

  1. Place some items in cart and go to checkout
  2. Fill required fields
  3. Input ONLY numbers (i.e. '001') in City* field

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?

  • 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

@ArturDivante ArturDivante added the bug Bug reports label Oct 17, 2019
@pkarw pkarw added the P3: Normal Priority mark - normal priority label Oct 17, 2019
@pkarw pkarw modified the milestones: 1.11.0-rc2, 1.10.4 Oct 17, 2019
@dz3n dz3n self-assigned this Oct 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug reports P3: Normal Priority mark - normal priority
Projects
None yet
Development

No branches or pull requests

4 participants