Customer Name Prefix shows white space when extra separator is addes.

[sskulkarni]

White space option is added when extra separator is added.

Preconditions

1. php7.1
2. Magento 2.2.5

Steps to reproduce

1.In admin menu Store->Configuration
Select "Customer Configuration" under confifuration.
Add "Mr;Ms;Mrs;" in "Prefix Dropdown Options"

Expected result

1. It should avoid the white space option, if extra separator is added.

Actual result

1.It is displaying extra white space option, and In case of it is required, It throws validation.

[magento-engcom-team]

Hi @sskulkarni. 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-engcom-team give me {$VERSION} instance

where {$VERSION} is version tags (starting from 2.2.0+) or develop branches (2.2-develop +).
For more details, please, review the Magento Contributor Assistant documentation.

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

• yes
• no

[sskulkarni]

@magento-engcom-team give me 2.2.5 instance

[magento-engcom-team]

Hi @sskulkarni. Thank you for your request. I'm working on Magento 2.2.5 instance for you

[magento-engcom-team]

Hi @sskulkarni, here is your Magento instance.
Admin access: https://i-17861-2-2-5.engcom.dev.magento.com/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[sskulkarni]

@magento-engcom-team
Reproduced in above instance.

[engcom-backlog-nickolas]

Hello @sskulkarni, thank you for your report.
We've acknowledged the issue and added to our backlog.

[osrecio]

What is exactly the problem? If you decide select the empty dropdown the validation shout out : "This is a required field." I think is a expected result

Thanks!

[sskulkarni]

No, Actually Required field is not a problem.
Problem is that is we add "Mr;Ms;Mrs;" in admin.
The front end should reflect 3 dropdowns

1. Mr
2. Ms
3. Mrs
   But now It shows

1: Mr
2: Ms
3: Mrs
4:

It should not consider the empty field and should be avoided by code.
Thanks.

[osrecio]

but if you select the 4th option you get an error validation

[sskulkarni]

Yes, that's fine, But my concern is 4th position should not display.
Only 3 dropdowns should.
Because It leads to confusion.
Thanks

[osrecio]

Ok that's ok.
Maybe someone from Magento will can help us to determine if is an issue.

[osrecio]

@engcom-backlog-nickolas Can you help to decide if is issue or not?

[ronak2ram]

Hello @sskulkarni
Semicolon (;) separated values means put Semicolon (;) for separate two value.
You have to put like Mr;Ms;Mrs
Not need last Semicolon (;)

I think this not an issue.

[nainesh2jcommerce]

I am currently working with Magento version 2.1.9 and facing same issue.

[magento-engcom-team]

Hi @shikhamis11. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your want to validate it one more time, please, go though the following instruction:

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

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

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

• 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[shikhamis11]

#MM19IN

[magento-engcom-team]

Hi @sskulkarni. Thank you for your report.
The issue has been fixed in #20896 by @shikhamis11 in 2.3-develop branch
Related commit(s):

• 8ff4aa55e320cb9facba7149ca71bca3b5ecebea
• fa72ee7f925963020ec5f5af558abff09fa4795b

The fix will be available with the upcoming 2.3.2 release.

[magento-engcom-team]

Hi @sskulkarni. Thank you for your report.
The issue has been fixed in #21245 by @mage2pratik in 2.2-develop branch
Related commit(s):

• 77c780d5ae54a8ec982648d6104cff6da50e35a6
• 5eeecac645d53a3c543247a1d6e6c26752ee5012
• 69cf6cebcd8ad8d51dc3d88fe89b6f3375bf311c

The fix will be available with the upcoming 2.2.9 release.