[2.3.6 & 2.4.1] Submitting invalid create account form leaves the submit button disabled

[hostep]

Preconditions (*)

1. Magento 2.3.6 and 2.4.1
2. Confirmed on 2.4.1 composer installation
   Note(16 oct 2020): on git 2.4-develop branch it possibly not reproducible because the branch is not synced with release code yet

Intitial case for 2.3.6

Steps to reproduce (*)

1. Install clean Magento 2.3.6 or 2.4.1
2. Go to the create a new account form
3. Press the 'Create an Account' button without filling in any fields
4. Notice that the button turns inactive/disabled

Expected result (*)

1. Button should stay active/enabled

Actual result (*)

1. Button stays disabled, even after filling in all required fields, so you can't submit the form

Case for 2.4.1

Steps to reproduce (*)

1. Go to Create New Customer Account
2. Fill form but do some mistake e.g. in password fields. Example:
   -- password/Confirm password is not equal
   -- password/Confirm password is not long enough
3. Click "Create an Account" button
4. Result: Form validation is failed and "Create an Account" button is not clickable(disabled)
5. Correct/fix a mistake(s)

Expected result (*)

1. Button should stay active/enabled
2. User should be able to create new account

Actual result (*)

1. Button stays disabled, even after filling in all required fields with valid/correct data
2. Customer is NOT able to create new Account

Discussion

This is pretty bad because when people make a single mistake on a form, they can no longer submit the form after correcting their mistake, they need to refresh the form and loose all the data they entered and enter them again.

Maybe other forms are affected as well, not tested yet...

 

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• < ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ > Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

| Patch is released in MQP|borderStyle=dashed|borderColor=#cccccc|titleBGColor=#dddddd|bgColor=#e3ffea |
| --- |
|

• MQP release:
  1.0.11

• Patch ID
  MC-38509

• Are there any additional actions required after the patch installation to make it work?
  N/A

• Compatible with Magento versions:
  Magento Commerce and Magento Commerce Cloud 2.3.6, 2.4.1
  Check using Patch Checker tool

• Fix version
  2.4.2 |

 

[m2-assistant]

Hi @hostep. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[hostep]

Update: just tested Magento 2.4.1 and it also has this problem, so updated title and details in opening post.

[sdzhepa]

Hello @hostep

I am also checking this issue on 2.4.1.
And noticed that the button became unblocked as soon as a user filled email field
need 10-15min and i will attach the recording

[hostep]

Hi @sdzhepa : just tested again on 2.4.1 and I can't confirm, the button stays disabled.

I did some quick git bisecting between 2.4.0 and 2.4.1 and it says this commit causes the bug: 02b87f6

[hostep]

Hmm, something fishy is going on, it works in 2.4.1 when you fill in the email field as last one (but not on 2.3.6) but it fails when you fill in the password field or your last name as last one.

There is definitely something weird going on.

[hostep]

It does work correctly on the 2.4-develop branch, but I don't know if the 2.4.1 code is already merged in there ....

Anyway, have to leave, time for the weekend to start! 🙂

[sdzhepa]

@hostep
After little-bit deep investigation, i found steps to reproduce it.
Thank you for report!

If you not mind i will update the description and steps to reproduce

Steps:

1. Go to Create New Customer Account
2. Fill form but do some mistake e.g. in password fields. Example:
   -- password/Confirm password is not equal
   -- password/Confirm password is not long enough
3. Click "Create an Account" button
4. Result: Form validation is failed and "Create an Account" button is not clickable(disabled)
5. Correct/fix a mistake(s)

Expected result (*)

1. Button should stay active/enabled
2. User should be able to create new account

Actual result (*)

1. Button stays disabled, even after filling in all required fields with valid/correct data
2. Customer is NOT able to create new Account

[magento-engcom-team]

✅ Confirmed by @sdzhepa
Thank you for verifying the issue. Based on the provided information internal tickets MC-38509 were created

Issue Available: @sdzhepa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.