Why does required still fail submit when Form is novalidate?

Form defaults to novalidate, so the browser never runs native constraint validation. required on Input and NumberField still registers a presence rule with the Form, so empty required fields make submit() return false.

Why does my @submit handler run even when the form is invalid?

@submit is pass-through — it fires on every native submit regardless of validity. Guard inside the handler: read the valid flag from the payload and return early when it's false.

How do I keep two forms on the same page from interfering?

Give each a namespace that contains : (e.g. namespace="v0:billing") and set the same value on each field's form-namespace. Sibling forms are already isolated by Vue's nearest provide; the custom key is for useForm('v0:billing') from outside the tree and for fields that would otherwise inject the default 'v0:form'.

Why doesn't calling submit() from slot props emit the @submit event?

submit() and reset() from slot props invoke the form methods directly. The @submit and @reset events only fire from native form submission or reset.

Form

A form wrapper that coordinates validation across child input fields and handles submit/reset events.

Markdown

PreviewRenders elementIntermediateOct 13, 2026

Usage

Wrap your inputs in <Form>. Native <button type="submit"> and <button type="reset"> work as expected.

Theme

Mode

Palettes

Accessibility

basic.vue

<script setup lang="ts">
  import { Form, Input } from '@vuetify/v0'
  import { shallowRef } from 'vue'

  const valid = shallowRef<boolean | null>(null)
  const email = shallowRef('')
  const password = shallowRef('')
  const submitted = shallowRef(false)

  function onSubmit ({ valid }: { valid: boolean }) {
    if (!valid) return

    submitted.value = true
  }

  function onReset () {
    email.value = ''
    password.value = ''
    submitted.value = false
  }
</script>

<template>
  <Form v-model="valid" class="flex flex-col gap-4 max-w-sm mx-auto" @reset="onReset" @submit="onSubmit">
    <Input.Root
      id="email"
      v-model="email"
      label="Email"
      :rules="[
        v => !!v || 'Email is required',
        v => /.+@.+\..+/.test(v as string) || 'Must be a valid email',
      ]"
      type="email"
    >
      <label class="text-sm font-medium text-on-surface" for="email">Email</label>

      <Input.Control
        class="w-full px-3 py-2 rounded-lg border border-divider bg-surface text-on-surface placeholder:text-on-surface-variant/50 outline-none data-[focused]:border-primary data-[state=invalid]:border-error transition-colors"
        placeholder="you@example.com"
      />

      <Input.Error v-slot="{ errors }" class="text-xs text-error">
        <span v-for="error in errors" :key="error">{{ error }}</span>
      </Input.Error>
    </Input.Root>

    <Input.Root
      id="password"
      v-model="password"
      label="Password"
      :rules="[
        v => !!v || 'Password is required',
        v => (v as string).length >= 8 || 'Must be at least 8 characters',
      ]"
      type="password"
    >
      <label class="text-sm font-medium text-on-surface" for="password">Password</label>

      <Input.Control
        class="w-full px-3 py-2 rounded-lg border border-divider bg-surface text-on-surface placeholder:text-on-surface-variant/50 outline-none data-[focused]:border-primary data-[state=invalid]:border-error transition-colors"
        placeholder="••••••••"
      />

      <Input.Error v-slot="{ errors }" class="text-xs text-error">
        <span v-for="error in errors" :key="error">{{ error }}</span>
      </Input.Error>
    </Input.Root>

    <div class="flex gap-2">
      <button
        class="px-4 py-2 rounded-lg bg-primary text-on-primary font-medium text-sm"
        type="submit"
      >
        Sign in
      </button>

      <button
        class="px-4 py-2 rounded-lg border border-divider text-on-surface text-sm"
        type="reset"
      >
        Reset
      </button>
    </div>

    <p v-if="submitted" class="text-sm text-success">
      Form submitted successfully!
    </p>
  </Form>
</template>

Anatomy

vue

<script setup lang="ts">
  import { Form, Input } from '@vuetify/v0'
</script>

<template>
  <Form>
    <Input.Root>
      <Input.Control />

      <Input.Error />
    </Input.Root>
  </Form>
</template>

Architecture

Form creates a createForm instance and provides it via useForm(). Child validations auto-register on mount and unregister on unmount.

The @submit event is pass-through — it always fires, regardless of validity. Guard in your handler:

function onSubmit ({ valid }: { valid: boolean }) {
  if (!valid) return
  // handle submission
}

Examples

A complete account registration form that shows how Form coordinates validation across several Input.Root fields and reports a single aggregate result. The form gathers name, email, password, and a confirmation, validates each field on blur, and only commits when every child validation passes.

The confirmation field’s rule compares its value against the live password model rather than a static value, so changing the password re-evaluates whether the two still match. Because Form’s @submit event is pass-through — it fires on every native submit regardless of validity — the handler guards on payload.valid before doing any work, then simulates a server-side duplicate-account check that surfaces through the email field’s error / error-messages props. The composable owns the field state and the submitted/server-error flags, so the entry component can swap the form for a success panel without the form needing to know about it.

Reach for this pattern whenever a form is more than a single field: extract the state and submit logic into a use* composable, keep the markup in a reusable component, and let the entry wire them together. For the underlying validation primitives, see createForm and createValidation; for individual field anatomy, see Input.

File	Role
`useSignup.ts`	Composable — field state, submit/reset logic, simulated server error
`SignupForm.vue`	Reusable component — renders the `Form` with four validated `Input.Root` fields and a cross-field match rule
`signup-form.vue`	Entry — wires the composable to the form and swaps in a success panel on submit

Try submitting with taken@example.com to see server-side error injection.

Theme

Mode

Palettes

Accessibility

Recipes

Slot Props

Use slot props for reactive form state in the template:

vue

<template>
  <Form v-slot="{ isValid, isValidating, submit, reset }">
    <!-- Inputs -->

    <button type="submit" :disabled="isValidating">
      {{ isValidating ? 'Validating…' : 'Submit' }}
    </button>

    <p v-if="isValid === false">Please fix the errors above.</p>
  </Form>
</template>

Disabled / Readonly

The disabled and readonly props propagate to the form context. Child components can read them via useForm():

vue

<template>
  <Form disabled>
    <!-- All fields read form.disabled via useForm() -->
  </Form>
</template>

Custom Namespace

Use namespace to isolate multiple forms on the same page. Keys must contain :. Child fields join via form-namespace — the same pairing as group-namespace on Toggle/Checkbox/Radio.

vue

<template>
  <Form namespace="v0:billing">
    <Input.Root form-namespace="v0:billing" />
  </Form>

  <Form namespace="v0:shipping">
    <Input.Root form-namespace="v0:shipping" />
  </Form>
</template>

form on Input is the HTML form="id" attribute. form-namespace is the DI key. Defaults match (v0:form), so a single unnamed Form needs no extra prop.

Programmatic Submit

Call submit() from slot props when you need to trigger validation without a submit button:

vue

<template>
  <Form v-slot="{ submit }">
    <!-- Inputs -->

    <button type="button" @click="submit">Save Draft</button>
  </Form>
</template>

Calling submit() or reset() via slot props invokes the form methods directly and does not emit @submit or @reset. Those events only fire from native form submission/reset.

Accessibility

Form renders a native <form> element, so all standard form semantics apply. No custom ARIA is needed — the browser handles submit on Enter, associates labels with inputs via id/for, and reports validation errors to assistive technology through child inputs.

Keyboard Interaction

Key	Behavior
`Enter` (in input)	Submits the form
`Escape`	No default behavior — handle in your submit handler

FAQ

Discord

Need help? Join our community for support and discussions ↗

API Reference

The following API details are for all variations of the Form component.

Form

5 props, 3 events, 1 slot