Currently, type="text" inputs are treated strictly as string values. When used with inputmode="numeric" and bound to a numeric signal field, this results in a next error :

 TS2322 error number is not assignable to string

Allows inputs configured with inputmode="numeric" to properly synchronize with signal-based form fields by accepting and normalizing both string and number values. This aligns with accessibility practices ( due to assistive technology issues e.g., problematic spinner controls and screen reader behavior) while still preserving the numeric keyboard on mobile

@Component({
  template: `
      <input
        type="text"
        inputmode="numeric"
        [formField]="f.documentNumber"    
      />
  `,
})
class InputModeExample {
  readonly data = signal({
    documentNumber: 4,
  });

  readonly f = form(this.data);
}

Other information

This addresses part of #66903 by enabling proper support for inputmode="numeric" with numeric form fields.

However, on iOS, pattern="[0-9]*" is often required to consistently trigger the numeric keypad. Since pattern is currently disallowed with [formField], that aspect remains unresolved and would need to be considered separately. ( Although we can currently use modifying the DOM directly as a workaround to add it at runtime )