Form state tracking (dirty, touched, valid) in Angular - Step-by-Step Execution

Concept Flow - Form state tracking (dirty, touched, valid)

User focuses input

↓

User changes input value

↓

Control becomes dirty

↓

User blurs input

↓

Control becomes touched

↓

Control is valid or invalid

↓

Form state updates

This flow shows how Angular tracks form control states: when a user focuses, changes, and leaves an input, Angular updates touched, dirty, and valid states accordingly.

Execution Sample

Angular

import { Component } from '@angular/core';
import { FormControl, Validators } from '@angular/forms';

@Component({ selector: 'app-form', standalone: true, template: `
  <input [formControl]="nameControl" aria-label="Name input" />
  <p *ngIf="nameControl.touched && nameControl.invalid">Name is required.</p>
` })
export class FormComponent {
  nameControl = new FormControl('', Validators.required);
}

This Angular component tracks a name input's touched, dirty, and valid states with a required validator.

Execution Table

Step	User Action	touched	dirty	valid	Message Shown
1	Page loads, input empty	false	false	false	No
2	User focuses input	false	false	false	No
3	User types 'A'	false	true	true	No
4	User deletes input (empty)	false	true	false	No
5	User blurs input	true	true	false	Yes
6	User types 'John'	true	true	true	No

💡 User finishes interaction; form control states reflect user input and validation.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6
touched	false	false	false	false	true	true
dirty	false	false	true	true	true	true
valid	false	false	true	false	false	true

Key Moments - 3 Insights

Why does 'touched' become true only after the user blurs, not just on focus?

'touched' becomes true when the user leaves the input after focusing it, not immediately on focus. In the execution_table, after step 2 (focus), touched is still false; it becomes true after blurring (step 5).

Why is 'dirty' false at first and true after typing?

'dirty' means the user changed the input value from its initial state. Initially (step 1 and 2), no changes happened, so dirty is false. After typing (step 3), dirty becomes true as shown in the table.

When does the control become invalid?

The control is invalid when the input is empty but required. At step 4 and 5, the input is empty, so valid is false, triggering the error message.

Visual Quiz - 3 Questions

Look at the execution table, what is the 'dirty' state after the user focuses the input but before typing?

A true

B false

C undefined

D null

💡 Hint

Check the 'dirty' column at Step 2 in the execution_table.

At which step does the control become invalid?

A Step 3

B Step 2

C Step 4

D Step 6

💡 Hint

Look at the 'valid' column and 'Message Shown' in the execution_table.

If the user never types anything and blurs the input, what would the 'touched' and 'dirty' states be?

A touched: true, dirty: false

B touched: false, dirty: false

C touched: true, dirty: true

D touched: false, dirty: true

💡 Hint

Recall that 'touched' updates on blur, 'dirty' only on value change.

Concept Snapshot

Angular Form Control states:
- touched: true after input loses focus
- dirty: true after input value changes
- valid: true if input passes validators
Use these to show validation messages and track user interaction.

Full Transcript

This visual execution shows how Angular tracks form control states: touched, dirty, and valid. Initially, all states are false. When the user focuses the input, touched remains false until the input loses focus. Typing changes the value, setting dirty to true. Validation runs after each change, updating valid. If the input is empty but required, valid becomes false, showing an error message. This helps developers give feedback only after user interaction.

Practice

1. In Angular forms, what does the dirty state indicate about a form control?

easy

A. The input has passed validation rules.

B. The user has changed the input value.

C. The user has focused and then left the input.

D. The form control is disabled.

Solution

1. Step 1: Understand the meaning of dirty in Angular forms

   The dirty state means the user has changed the value of the input from its original value.

2. Step 2: Compare with other states

   touched means the user focused and left the input, valid means the input passes validation, and disabled means the control is inactive.

3. Final Answer:

   The user has changed the input value. -> Option B

4. Quick Check:

   dirty = user changed input [OK]

Hint: Dirty means input value changed by user [OK]

Common Mistakes:

• Confusing dirty with touched state
• Thinking dirty means input is valid
• Assuming dirty means input is disabled

2. Which of the following is the correct way to check if a form control named email is touched in an Angular template?

easy

A. form.controls.email.touched

B. form.email.touched()

C. form.get('email').isTouched

D. form.controls['email'].isTouched()

Solution

1. Step 1: Recall Angular form control access syntax

   In Angular, form controls are accessed via form.controls.controlName or form.get('controlName'). The touched property is a boolean, not a method.

2. Step 2: Identify correct property usage

   form.controls.email.touched correctly accesses the touched property. Other options incorrectly use method calls or wrong property names.

3. Final Answer:

   form.controls.email.touched -> Option A

4. Quick Check:

   Access touched as property, not method [OK]

Hint: Use .controls.name.touched without parentheses [OK]

Common Mistakes:

• Using parentheses like a method on touched
• Using incorrect property names like isTouched
• Accessing controls incorrectly with dot vs bracket

3. Given this Angular reactive form control initialization:

this.form = new FormGroup({
  username: new FormControl('', Validators.required)
});

// User focuses on username input, types 'John', then leaves the input.

What will be the values of dirty, touched, and valid for username after these actions?

medium

A. dirty: true, touched: true, valid: false

B. dirty: false, touched: true, valid: true

C. dirty: true, touched: false, valid: false

D. dirty: true, touched: true, valid: true

Solution

1. Step 1: Analyze user actions on the form control

   User focused and left the input, so touched is true. User changed the value from empty string to 'John', so dirty is true.

2. Step 2: Check validation status

   The control has Validators.required. Since 'John' is not empty, the control is valid, so valid is true.

3. Final Answer:

   dirty: true, touched: true, valid: true -> Option D

4. Quick Check:

   Changed + left + valid input = dirty, touched, valid true [OK]

Hint: Changed input + left focus + valid value = all true [OK]

Common Mistakes:

• Assuming dirty is false if user leaves input
• Confusing touched with dirty
• Thinking valid is false if user typed anything

4. You have this Angular template snippet:

<input type="text" formControlName="email">
<div *ngIf="form.controls.email.dirty && form.controls.email.valid">Valid email changed!</div>

But the message never shows even after typing a valid email. What is the likely problem?

medium

A. The form control is not marked as touched, so the message won't show.

B. The valid property is misspelled and should be isValid.

C. The form control might have an email validator, so valid is false.

D. The dirty property does not update on user input.

Solution

1. Step 1: Understand the condition for showing the message

   The message shows only if the control is both dirty and valid.

2. Step 2: Check if validation is set up

   If the form control has an email validator but the input doesn't pass it (even if it looks valid), valid is false, so the message won't appear.

3. Final Answer:

   The form control might have an email validator, so valid is false. -> Option C

4. Quick Check:

   Missing validator means valid stays false [OK]

Hint: Check validators if valid never becomes true [OK]

Common Mistakes:

• Thinking touched affects this condition
• Using wrong property names like isValid
• Assuming dirty never updates on input

5. You want to disable the submit button in an Angular reactive form until the user has changed at least one input and all inputs are valid. Which condition correctly implements this logic in the template?

<button [disabled]="???">Submit</button>

hard

A. [disabled]="form.pristine || form.invalid"

B. [disabled]="!form.touched || !form.valid"

C. [disabled]="form.touched && form.valid"

D. [disabled]="!form.dirty && !form.valid"

Solution

1. Step 1: Understand form state properties

   pristine means no changes made, opposite of dirty. invalid means form is not valid.

2. Step 2: Translate requirement to condition

   Disable button if form is pristine (no changes) or invalid (not valid). So disable when form.pristine || form.invalid.

3. Final Answer:

   [disabled]="form.pristine || form.invalid" -> Option A

4. Quick Check:

   Disable if no changes or invalid [OK]

Hint: Disable if pristine or invalid to require change and validity [OK]

Common Mistakes:

• Using dirty instead of pristine incorrectly
• Confusing valid with invalid
• Using touched instead of dirty/pristine