Checkout: Region select autofillable even if Allow to Choose State if It is Optional for Country is set to No

[mattijv]

Preconditions (*)

1. Magento 2.4.2 with sample data
2. United States removed from General > General > State Options > State is Required for
3. Allow to Choose State if It is Optional for Country is set to No

4. Browser has an address saved with United States as the country and California as the region (e.g. go to Settings > Autofill > Addresses and more in Chrome and add an address in United States and California as the region). I only tested this with Chrome, unsure if other browsers are affected.

Note: the country can be any country with regions, this is just an example.

Steps to reproduce (*)

1. Add item to the cart
2. Go to the checkout and apply the autofill to the shipping address (in Chrome start typing the name you selected and it should prompt for the autofill).
3. Select shipping method and go to the next step

Expected result (*)

1. The region input is NOT filled.

Actual result (*)

1. The region input IS filled.

This is problematic as the customer can't see the field and does not know if a wrong region is filled there. We have several orders that have the wrong region in the address as a result of this.

---

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”.

[m2-assistant]

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

[m2-assistant]

Hi @engcom-Hotel. 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.

[engcom-Hotel]

Hi @mattijv,

We have followed the exact steps, you have mentioned in the description. But we are unable to reproduce the issue. We are getting region name on checkout page. Please find below screenshot for reference:

Let us know if any other step(s), you have followed.

Thanks

[mattijv]

@engcom-Hotel Thank you for taking a look, but by your own screenshots you show that you have in fact managed to reproduce the issue: there is no region field visible on the checkout but the region is autofilled to the address. That is the problem.

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @konrad-szwed-accenture. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @konrad-szwed-accenture, here is your Magento Instance: https://5f6ee931e8c5f93b427faf2f2084946f-2-4-develop.instances.magento-community.engineering
Admin access: https://5f6ee931e8c5f93b427faf2f2084946f-2-4-develop.instances.magento-community.engineering/admin_4339
Login: 95d97fa4
Password: ee76bb5fa1aa