material-components / material-components/material-web
md-radios share same single selection group, ignoring associated forms.
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 11.3k
- Forks
- 1.1k
- Avg merge
- 20h 28m
- Merged PRs (30d)
- 13
Description
### What is affected?
Component
### Description
Opposed to native radio behavior, ``s with same name within different forms share the same single selection group. If associated, form should have higher priority over root node (document) for querying radios of same name.
### Reproduction
In the next [stackblitz](https://stackblitz.com/edit/webpack-webpack-js-org-rhkgju?file=dist%2Findex.html) you can see the difference in behavior. (queueMicrotask was replaced with setTimeout following [this issue](https://github.com/material-components/material-web/issues/5398)
### Workaround
None
### Is this a regression?
No or unsure. This never worked, or I haven't tried before.
### Affected versions
1.1.1
### Browser/OS/Node environment
Browser: Chrome/121.0.0.0 Safari/537.36 Edg/121.0.0.0
OS: Windows NT 10.0; Win64; x64
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the linked StackBlitz reproduction and inspect the md-radio form and name behavior first. Done means same-name radios in separate associated forms can each select independently, matching native radio behavior; verify this with a focused component test if the repository provides one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, javascript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100