Feature Request: Hide the Submit button until required fields are filled

I’d like to share a UX pattern I’m trying to implement and ask whether it’s currently possible — and if not, whether it’s on the roadmap.

The pattern: Hide the form’s Submit (“Send”) button until the visitor has made at least one meaningful interaction — specifically, until they’ve selected an answer to a required pre-qualifying radio button at the top of the form.

Why this is useful:

When using a “Who is this for?” radio at the top of a form (e.g., “I am a parent enrolling a child” / “I am an adult enrolling myself”), the fields shown below change based on the selection. If the Submit button is visible before any selection is made, the visitor might try to submit an incomplete, pre-conditional form — or it just looks cluttered with a big button sitting below a mostly-hidden form.

Hiding the button until the radio is answered gives a cleaner, more guided experience:

1. Visitor lands on the form — only the radio is visible, Submit is hidden.
2. Visitor selects their role — the relevant fields appear, and the Submit button appears.
3. Visitor fills in their details and submits.

What I’ve tried:

Forminator’s conditional logic can show/hide fields based on other field values. I’ve been able to use this on regular fields. However, I have not found a way to apply a “show when…” condition to the Submit button itself.

My questions / suggestions:

1. Is it currently possible to apply conditional logic to the Submit button in Forminator? If so, how?
2. If not, is this something that could be added? Even a simple “Show Submit button only when [field] is not empty / equals [value]” rule would cover most use cases.
3. As a workaround, would it be feasible to use a custom CSS class on the submit button row and toggle its visibility via JS based on the radio state? Is there a stable hook or wrapper class to target?

This pattern would be especially valuable for multi-audience forms (lesson inquiries, service bookings, intake forms) where the form structure changes based on who’s filling it out, and you want the Submit button to feel like a natural endpoint rather than a premature prompt.

Thanks for looking!