ngForm directive and form state in Angular - Step-by-Step Execution

Concept Flow - ngForm directive and form state

User opens page with form

↓

Angular creates <form> element

↓

ngForm directive attaches

↓

Form controls register with ngForm

↓

User interacts with controls

↓

ngForm updates form state: valid, dirty, touched

↓

Form state available for template and logic

Angular creates a form element, attaches ngForm directive, registers controls, and tracks form state as user interacts.

Execution Sample

Angular

<form #myForm="ngForm">
  <input name="email" ngModel required>
  <button [disabled]="!myForm.valid">Submit</button>
</form>

A simple form with ngForm directive tracking validity and disabling submit if invalid.

Execution Table

Step	Action	Form State (valid, dirty, touched)	Control State (email)	Button Disabled
1	Page loads, form created	valid: false, dirty: false, touched: false	valid: false, dirty: false, touched: false	true
2	User focuses email input	valid: false, dirty: false, touched: false	valid: false, dirty: false, touched: false	true
3	User types '[e-mail]'	valid: true, dirty: true, touched: false	valid: true, dirty: true, touched: false	false
4	User blurs email input	valid: true, dirty: true, touched: true	valid: true, dirty: true, touched: true	false
5	User clears email input	valid: false, dirty: true, touched: true	valid: false, dirty: true, touched: true	true
6	User submits form	valid: false, dirty: true, touched: true	valid: false, dirty: true, touched: true	true

💡 Form remains invalid after clearing input, submit button stays disabled.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6
myForm.valid	false	false	true	true	false	false
myForm.dirty	false	false	true	true	true	true
myForm.touched	false	false	false	true	true	true
email.valid	false	false	true	true	false	false
email.dirty	false	false	true	true	true	true
email.touched	false	false	false	true	true	true
button.disabled	true	true	false	false	true	true

Key Moments - 3 Insights

Why is the form invalid at the start even though no input was touched?

At step 1, the form is invalid because the required email input is empty. The form validity depends on control validity, not user interaction yet.

What does 'dirty' mean and when does it change?

Dirty means the user changed the input value. At step 3, typing '[e-mail]' sets dirty to true. Before that, it was false.

Why does the submit button disable again after clearing the input?

At step 5, clearing the input makes the email invalid again, so form.valid becomes false and button.disabled becomes true.

Visual Quiz - 3 Questions

Look at the execution table, what is the form's 'touched' state after step 3?

A true

B undefined

C false

D null

💡 Hint

Check the 'Form State' column at step 3 in the execution_table.

At which step does the submit button become enabled?

A Step 3

B Step 1

C Step 5

D Step 6

💡 Hint

Look at the 'Button Disabled' column in the execution_table.

If the email input was never touched, what would be the form's 'dirty' state at step 6?

A true

B false

C null

D undefined

💡 Hint

Refer to the 'dirty' state changes in variable_tracker for myForm and email.

Concept Snapshot

ngForm directive attaches to <form> and tracks form state.
Controls register with ngForm and update validity, dirty, touched.
Form state updates as user interacts.
Use form.valid, form.dirty, form.touched in template.
Submit button can disable based on form.valid.
ngForm simplifies reactive form state management.

Full Transcript

When Angular loads a form with the ngForm directive, it creates a form element and attaches the directive. Each input control inside registers with ngForm. The form tracks states like valid, dirty, and touched based on user interaction. Initially, the form is invalid because required inputs are empty. When the user types a valid email, the form becomes valid and dirty. Blurring the input sets touched to true. Clearing the input again invalidates the form and disables the submit button. This process helps developers easily manage form state and control UI behavior like disabling buttons.