Address fields filling out fails on checkout pages of Magento 2

Oxidant

Personalities aren't filled out correctly on almost all Magento 2 websites on checkout screen.Emails, password, etc work perfectly but almost all eCommerce websites ask for 2 Address fields (Street 1 line, Street 2 line). But 1password puts the adress into 2nd field only and skips the 1st one. However in source code it marked as "edited". On Magento 1 websites it worked fine but on Magento 2 not.

---

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided

Oxidant

AGAlumB

@Oxidant: Interesting. Thanks for getting in touch about this! Can you give me the URL for a site using this so I can test it? Also, which OS, 1Password, and browser version are you using? Thanks in advance!

adi

Hello.

The issue that I'm having is with the 1pass X and the standard 1pass browser extension. Is the same issue on firefox/safari/chrome.
When you autofill the address, the street name gets autofilled on the second address field, not the first one.
check this gif for the issue: https://shero.d.pr/LYzbsB
on the same gif, you going to see that the state is also not selected.
To note that the same issue is on all Magento 2 store that I'm working with. on Magento 1 the address autofill works fine.
to do testing you can use these two websites:
Magento 2: painfulpleasures.com
Magento 1: beautyplussalon.com

Thanks

---

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided

littlebobbytables

Greetings @adi,

I have a couple of questions if that's okay. Is it this Magento (https://magento.com/) and is it their Magento Commerce offering? Regarding the form, is it either based on their template or generated as standard by their code? I just want to make sure I've got a full understanding for filing the report :smile:

adi

Hello,

Yes, that us the platform I'm referring to.
The form that I filled on the provided gif, is the default template that they have on the checkout. I'm not sure if I understood correctly you question tho on what is the difference between their template and generated by their code that you mentioned.

Thanks

littlebobbytables

Hi @adi,

Cheers, I just wanted to gain a feeling as to how uniform the form would be over implementations. I'll make sure a report is filed to see what we can do.

ref: xplatform/brain#20, xplatform/filling-issues#249

scottsb

I just came here to post this same question. If it's helpful for the 1PW team, you can try this for yourself with this demo store to show that it is true of just plain vanilla Magento (i.e., just the framework with the default theme and no changes):
http://magento2-demo.nexcess.net/

I thought the issue could be the field names, but I tried playing with this myself in a dev environment of Magento 2, including the suggestions in both these articles, but it didn't seem to help:

https://support.1password.com/compatible-website-design/

https://developers.google.com/web/fundamentals/design-and-ux/input/forms/#use_metadata_to_enable_auto-complete

Unfortunately it's hard to diagnose further since the 1PW autofill engine is a black box.

@littlebobbytables You had asked whether this applies to the Magento Commerce offering specifically. Technically that is their commercially licensed product. It does apply to that, but it also applies to the Magento Open Source product that it's based on.

scottsb

This has been submitted again here, including links to demo sites:
https://discussions.agilebits.com/discussion/comment/469459

And note the issue is both that it fills the second address line (rather than the first) and fails to fill the state/region.

AGAlumB

@scottsb: Thanks! I'm not sure I see the benefit of having mutliple threads for the same issue though. What am I missing? Would it not be better to merge them?

scottsb

Definitely no need for two threads. I found the other one first and replied there. Then I found this one and posted that link to try to direct conversation there. If you have a way to officially merge them, that's perfect.

littlebobbytables

Hi @scottsb,

Thank you for those details and the example site, very handy :smile: The question was more because as I hadn't heard of Magento before I wanted to make sure I was looking at the right service given they seemed to offer a number of options. Thank you for the clarification.

scottsb

Magento is the one of the most common ecommerce platforms out there, so there's a pretty big cross-section of sites that could be fixed by addressing this. And because of their hybrid open source/commercial model, it spans both a ton of small retailers on the open source product but also some very big-name retailers on the commercial product.
https://trends.builtwith.com/shop/Magento

littlebobbytables

I did note Magento was part of Adobe when filing the report. While I don't know how prevalent it is I did work on the assumption that it was probably not niche given the parent company.

adi

hi @littlebobbytables is there any update or an ETA for releasing this, please?

ag_sebastian

Hi @adi, I'm afraid we don't have any updates yet, but thanks for bumping the thread. We haven't forgotten about this issue, but I can't tell you exactly when we'll be able to get to it.