Add equivalent `ngDefaultControl`-esque directives for additional value types

[geoff-ponnath-44115]

Which @angular/* package(s) are relevant/related to the feature request?

forms

Description

With Form Associated Custom Elements (FACE) now much more practical with advancements in the Element Internals API, its becoming easier to create a FACE that can be dropped into any framework. Currently, Angular has the ngDefaultControl directive that can be added to a FACE that uses a string value (for example <input type="text">) and allow it to be used with template driven and reactive forms, but thats not possible for other input types (for example a boolean <input type="checkbox">).

Proposed solution

There was already a PR that would solve this in 2022 but it was closed. However, the landscape has changed with updates to the Element Internals API, and FACEs are now a more practical solution for organizations that have multiple frameworks to support.

#45953

Alternatives considered

Custom directives can be added, or Angular wrappers for web components. With the existence of ngDefaultControl though, it would make sense to also have directives that address other input types.

[VaradGupta23]

Context
Angular’s built-in ngDefaultControl directive bridges the gap between native form controls and Angular forms (template-driven or reactive) by implementing ControlValueAccessor for string-valued inputs like .

With recent browser advancements in the Element Internals API, creating custom elements that natively participate in forms (FACE) is easier and more practical.

Currently, Angular’s ngDefaultControl only supports string values, which limits out-of-the-box support for FACEs with other data types (boolean, number, etc).

The feature request proposes:
Provide additional Angular directives akin to ngDefaultControl, each tailored for a specific value type, such as:

ngBooleanControl for boolean values (checkboxes, toggles)

ngNumberControl for numeric inputs

Possibly others for dates, files, or complex types

These directives would implement the appropriate ControlValueAccessor logic to connect Angular forms with FACEs that expose those types.

This would reduce the need for custom wrappers or manual directive creation when using FACE in Angular, easing integration.

Why is this useful now?
In 2022, a PR (#45953) tried to address this but was closed.

Since then, browser support and standards around FACE and Element Internals API have matured.

Many organizations now build cross-framework FACE web components, so having Angular directives that integrate cleanly with these controls would reduce duplication and improve developer experience.

Alternatives mentioned:
Developers currently write custom directives or wrappers to implement ControlValueAccessor for FACEs with non-string types.

While this works, it adds boilerplate and fragmentation.

Having official Angular directives like ngDefaultControl but for booleans, numbers, etc., would unify patterns and improve maintainability.

Summary
This is a feature enhancement proposal for Angular forms, to extend the convenience and integration level of ngDefaultControl-like directives to additional data types, enabling smooth support for Form Associated Custom Elements with different value types.