Feature Request: Native `autocomplete` attribute support on form fields

Workaround: Setting autocomplete attributes on Forminator fields via JavaScript

Problem:
Forminator does not support setting the HTML autocomplete attribute on form fields
natively. Without it, browsers skip autofill or guess incorrectly.

Solution:
Add a Custom HTML block to the page containing the form, with the script below.
It runs on DOMContentLoaded and sets the correct autocomplete values by targeting
fields by their name attribute. A MutationObserver re-applies the attributes if
Forminator re-renders any part of the form dynamically.

Field name mapping used (adjust to match your form):
name-2[first-name] -> given-name (Parent / Guardian first name)
name-2[last-name] -> family-name (Parent / Guardian last name)
name-1[first-name] -> off (Student first name — different person)
name-1[last-name] -> off (Student last name — different person)
email-1 -> email
phone-1 -> tel

— PASTE INTO CUSTOM HTML BLOCK —

— END —

Notes:

• Place this Custom HTML block BEFORE the Forminator block on the page.
• To add more fields, add entries to the map object using the field’s name
  attribute value (inspect the rendered input in browser DevTools to confirm).
• Common autocomplete token reference:
  given-name, family-name, name
  email
  tel
  organization
  street-address, address-line1, address-line2
  postal-code
  bday
  off (disables autofill for that field)
• See full spec: https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofill

Hi Amin, thanks for the detailed breakdown!

Good news — I just confirmed that name fields (given-name, family-name) and email are all working with native autocomplete as expected. That covers most of our form.

The remaining gap: phone field (tel) autocomplete

On a contact/inquiry form, tel autofill is arguably the most useful — it's the field users are most likely to have saved in their browser or password manager, and it's the one they're most likely to mistype.

Our specific request is:

Add a per-field toggle in the builder to enable/disable autocomplete on the phone field (and date, if the same issue applies).

We understand you disabled it by default due to reported issues — but those issues may not affect all use cases. Disabling globally with no override means every site has to work around it in JavaScript, which is fragile.

Even a simple checkbox — "Enable browser autofill for this field (advanced)" — would be enough. The site owner can accept any browser-specific quirks on their own form.

Our current workaround (for anyone else hitting this):

document.addEventListener('DOMContentLoaded', function() {
var el = document.querySelector('input[name="phone-1"]');
if (el) el.setAttribute('autocomplete', 'tel');
});

This works, but breaks silently if Forminator changes its field naming convention.

Thanks again for looking into this!