It's actually a very "simple" fix for you that would make it possible to put EPiServer Forms on drugs for customers, when using this on the fields where appropriate...

@Jonas, I have tried this on different input elements in Epi forms, but with a name format like name="__field_1285" it does not work for me. After just switching to name="name" for example it starts to work. Any idea if something changed or what I am missing? Thank you.

Here is an example of my full input code:

<input autocomplete="name" name="__field_100638" id="436fbd45-e12c-4f39-9c26-56023a3ac80c" type="text" class="FormTextbox__Input form-control" aria-describedby="__field_100638_desc" value="" data-f-datainput="" aria-invalid="false">

@alexandru.dumitru my suggestion is about Optimizely implementing support for the editors  to select a valid value for autocomplete, stating which type of data the input is, if it is a full name, first name, surname, email, etc., per input instance.

For it to really work in the browser you have to rely on other forms you have visited are stored in your browser, so it will autofill if it can identify that field type.

So, create multiple forms with the same value, and test if it is stored after a post, between different forms with inputs with the same autocomplete value.

Hi again!

At least in my tests, the suggestions seems correct.

Tested on iPhone yesterday.

You can also test the markup here: https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/autocomplete#try_it