[Resuelto] I need a way to intercept autocomplete="off" attribute for Google Maps Fields…

[Autor]

Mensajes

[shawnW-3]

Tell us what you are trying to do?
The over all goal is to prevent auto complete on the address field.

The reason is that autocomplete doesn't fill the entire address and we're only getting partial addresses - see screenshots.

I realize this is mostly a google chrome issue. I read that it can be blocked by tricking chrome into thinking the field is for a password, ie autocomplete="new-password". I would like to try this, but autocomplete="off" loads persistently. I tried using JS - loading in the header, footer, in the JS section of the forms, but nothing seems to work. I know the script runs because I can insert an attr for test="testproof" right after it.

Is there any documentation that you are following?
I read other support threads, both on Toolset and Stackoverflow. Toolset users haven't been very specific, but this is a major topic on the web in general.

Is there a similar example that we can see?
Screenshots show the real issue

What is the link to your site?
test3.ddaudio.com

If you have any other ideas on how to help me reach the overall goal that would be nice. I think this address field looks nice, functions well, and saves me from making other fields: address1, address2, city, state, zip, country.

[Waqar]

Hi Shawn,

Thank you for contacting us and I'd be happy to assist.

I see two different autocomplete features in your screenshots:

1. The first one that is shown in your screenshot "map_ui_1.jpg" is added using the Chrome browser.

On my test website with an address field in a Toolset Form, I couldn't see this autocomplete, because autocomplete="off" is added to that input field, by default.
( screenshot: enlace oculto )

If you're seeing this autocomplete feature in your browser without making any changes to the default address field's code, it could be related to the Chrome browser's local settings.

2. The second one that is shown in your screenshot "map_ui_2.jpg" is added by the Toolset which is linked to Google Maps so that a visitor can easily select the correct address or coordinates.

That autocomplete feature is not only useful in terms of user experience but also allows Google Location API to get the correct latitude/longitude coordinates for the selected location and then saves them as values in the corresponding address field.

If someone needs an address field to save the exact location information, I can't think of a case where disabling this second autocomplete feature would be helpful.

On the other hand, if you need a field, where a visitor can share the complete postal or human-readable address, it would be better to use a single-line field for that and not an address field.

If you'll save the address information as plain single-line text, it will be possible to still show it on the map, using the "address" attribute in the "wpv-map-marker" shortcode ( ref: https://toolset.com/documentation/user-guides/maps/maps-shortcodes/#wpv-map-marker ). However, operations like distance filters won't work with that field ( ref: https://toolset.com/documentation/user-guides/maps/display-on-google-maps/filtering-and-ordering-map-markers-by-distance/ ), since the field won't have the information in the form of latitude/longitude coordinates.

I hope this helps and please let me know if you need any further assistance around this.

regards,
Waqar

[shawnW-3]

This doesn't look like something easily solved. We decided to replace the google address with regular single lines.