angular / angular/components

Radios should have separate unique selection in different form containers

Open
#5,983 10 comments 4 reactions 0 assignees View on GitHub
area: material/radio help wanted P4
Dominant language
TypeScript
Stars
25k
Forks
6.8k
Avg merge
1d 8h
Merged PRs (30d)
91

Description

#### Bug, feature request, or proposal:
Bug

#### What is the expected behavior?
Radio group controls with the same name should not correlate with each other if they belong to different forms.

#### What is the current behavior?
If you change value in one radio group, then the value will be unset for all the other radio groups with the same name in other forms

#### What are the steps to reproduce?

```



{{season}}

Second form:



{{season}}

```

Providing a Plunker (or similar) is the *best* way to get the team to see your issue.
Plunker template: https://plnkr.co/edit/6xzFen4ayfMIv9JnYgW0?p=preview

#### What is the use-case or motivation for changing an existing behavior?
Currently it's impossible to implement a list (of similar items) if its items contain forms.

#### Which versions of Angular, Material, OS, TypeScript, browsers are affected?
@angular/cli: 1.2.0
node: 8.0.0
os: win32 x64
@angular/animations: 4.3.1
@angular/cdk: 2.0.0-beta.8
@angular/common: 4.3.1
@angular/compiler: 4.3.1
@angular/core: 4.3.1
@angular/forms: 4.3.1
@angular/http: 4.3.1
@angular/material: 2.0.0-beta.8
@angular/platform-browser: 4.3.1
@angular/platform-browser-dynamic: 4.3.1
@angular/platform-server: 4.3.1
@angular/router: 4.3.1
@angular/cli: 1.2.0
@angular/compiler-cli: 4.3.1
@angular/language-service: 4.3.1

Contributor guide

Open the contributing guide

Research direction

Start with the supplied Plunker reproduction and verify that identically named radio groups in separate forms currently affect one another. Trace the Angular Material radio-group behavior responsible, then add a regression test showing each form retains its own selection and run the relevant test suite.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular, typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.