Guest visitor e-mail in checkout kicks off password field visibility

[speedupmate]

Preconditions (*)

1. Magento 2.3.4

Steps to reproduce (*)

1. add items to cart and reach checkout , use a unregistered e-mail in e-mail field and fill address data
2. go back to cart page (or to any other page as long outside from checkout page)
3. then go back to checkout page and see that it presents password fields for authenticating for e-mail that is not registered

Expected result (*)

1. add items to cart and reach checkout , use a unregistered e-mail in e-mail field and fill address data
2. go back to cart page (or to any other page as long outside from checkout page)
3. then go back to checkout page and see that password fields are not displayed since e-mail is not jet registered

Actual result (*)

1. when reaching checkout and adding a unregistered e-mail and then visiting other pages and going back to checkout it shows password fields for unregistered visitors

2. this is happening cause of https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/Checkout/view/frontend/web/js/view/form/element/email.js#L196 and was introduced with 0861a30

[m2-assistant]

Hi @speedupmate. 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.

@speedupmate do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

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

[m2-assistant]

Hi @krishprakash. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[krishprakash]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @krishprakash. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @krishprakash, here is your Magento instance.
Admin access: https://i-26903-2-4-develop.instances.magento-community.engineering/admin_3b68
Login: 6cb9f73d Password: b0ea869be18f
Instance will be terminated in up to 3 hours.

[magento-engcom-team]

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

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