Tweet
Because our FaaS web page isn't autofilling correctly in Chrome, I started comparing FaaS field names to the form field names in the easyPage and Advanced Page forms. In FaaS, the fields start with "Billing" or "Shipping", whereas the FaaS field names start with "txt". I don't know if this affects Chrome autofill or not, but I'm curious why the difference. Is it something outside of customer control, or can I use the "txt" field names as well?
-
-
Good day!
Would you please post the link to your form so we can test it.
The form should autofill without any issues. We need to see your page and figure out what is going on.Regards,
Click & Pledge Support Department
Join us @ the educational webinars: https://clickandpledge.com/webinars/
Live Support- read more: https://support.clickandpledge.com/s/article/general-information-live-support/ -
Sure. It is http://www.ywamsf.org/test-donation-page-1.
I think it may have to do with the way we have the fields labeled. The labels appear in the text box itself. We modeled after a sister organization and their form does the same thing.
What is the story with the different prefixes: "Billing", "Shipping", "txt"?Comment
-
Good day!
I just did a test transaction and used Google Chrome
& it worked fine. All fields filled with the autofill without any issues.
Why do you think it is not working?Regards,
Click & Pledge Support Department
Join us @ the educational webinars: https://clickandpledge.com/webinars/
Live Support- read more: https://support.clickandpledge.com/s/article/general-information-live-support/Comment
-
Because it isn't working for me. My Chrome is version 33 and says it's up to date.
How did you test it? In the test I did just now, I double-clicked the email field and selected a profile I know to be complete. All contact fields were filled out except First Name, Last Name, and City.Comment
Comment