Skip to content

bug(radio-group): form scope is not respecated #27817

Open
@DaSchTour

Description

@DaSchTour

Is this a regression?

  • Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

Other than with vanilla radio buttons with angular material radio groups the form is not used as a scope. Radios groups with the same name interfere with each other even if in different forms. This makes it very hard to use them in template driven forms when wanting to pull the data from the NgForm value.

Reproduction

StackBlitz link: https://stackblitz.com/edit/vaq4dq?file=src%2Fexample%2Fradio-overview-example.html
Steps to reproduce:
1.
2.

Expected Behavior

The form element is used as a scope for radio-groups

Actual Behavior

Radio groups from all forms are connected by name

Environment

OS: linux x64

Angular: 16.1.1
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package Version

@angular-devkit/architect 0.1601.0
@angular-devkit/build-angular 16.1.0
@angular-devkit/core 16.1.0
@angular-devkit/schematics 16.1.0
@angular/cdk 16.2.4
@angular/cli 16.1.0
@angular/material 16.2.4
@angular/material-moment-adapter 16.2.4
@schematics/angular 16.1.0
rxjs 7.4.0
typescript 5.0.3

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentarea: material/radio

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions