growella / gravityforms-autocomplete-fields Goto Github PK

I have a multi-page form with inputs such as chained selects and multiple addresses and country choices throughout the form which differ, eg choice of jurisdiction country vs HQ location country of company. Autofill (without your plugin) is back-filling fields on prior pages overwriting data which the user has already entered, which is a disaster. It also resets 'chained-selects' dropdowns when it does this and triggers a gravitypdf-previewer on last page to reload, showing the new erroneous data when the customer is at final stage, filling their billing details and chooses say country for their billing address.

Google have now disabled the option to disable autofill and autocomplete in Chrome: https://stackoverflow.com/questions/47775041/disable-autofill-in-chrome-63

The only workaround to stop google interfering with your form fields it seems is to tell it the field label is some unsupported type like 'Leave_it_alone_1' instead of eg. country. On this plugin I am restricted to selecting one of the known labels. Can you add in the choice of making a new unsupported custom labels I can type in, as an alternative to your drop-down choices, so that it blocks chrome from trying to be 'helpful'.

I am not sure how or where I could do this manually.
Thank you.

Has this project been abandoned, or have you found that it works "good enough" in its current state?

The repo will need a properly-formatted readme.txt file that adheres to the WordPress.org plugin repository's standards.

The "gform_autocomplete_attribute_values" filter needs to be documented in the project's README file.

This has dependencies on #2, which is why it hasn't yet been written.

Need to determine the final format for the output of Core\get_autocomplete_values(); right now, it's a flat list, but a case could be made for supporting nested arrays to group similar types.

The autocomplete attribute specification supports more detailed values (e.g. "honorific-name", "given-name", "additional-name", etc.), which would make sense for complex fields like "Name".

Instead of just saying "the first input represents a name", we'd be able to say "when building a complex name field that has the autocomplete attribute of 'name', the first name has an autocomplete value of 'given-name', the last name is the 'family-name', etc."

To avoid false positives, the user would still have to assign "name" as the autocomplete attribute on the Gravity Forms field, but the inputs could then receive more appropriate values.