Skip to content

md-radio buttons in reactive forms (model based) cause several problems  #1875

Closed
@mLaird

Description

@mLaird

Bug, feature request, or proposal:

It is a bug, as best I can tell. I cannot tell whether the problem is in Angular or MD, code or docs.

What is the expected behavior?

md-radio buttons should not affect other DOM components, and they should work.

What is the current behavior?

1.When radio buttons are constructed in a reactive form with current Angular 2 docs, http://devdocs.io/angular~2_typescript/api/forms/index/radiocontrolvalueaccessor-directive , all the md-input elements disappear from the form page. When formControlName="something" is removed from md-radio-button elements, the md-input boxes re-appear. 2. Also when formControlName is present, the md-radio buttons do not switch from one to another. Each click adds another clicked circle to the group. When removed, only one click registers in each group, i.e., switch occurs. 3. Lastly, my radio button dots are not inside the circles, but I imagine that bug has already been reported.

What are the steps to reproduce?

I posted relevant code, and console errors at:
http://stackoverflow.com/questions/40597983/angular-2-md-radio-buttons-in-reactive-model-based-forms-dont-work-stop-md
I have tried a lot of things, and conclude the problem is a bug.

Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: http://plnkr.co/edit/o077B6uEiiIgkC0S06dd

What is the use-case or motivation for changing an existing behavior?

Make radio buttons behave as expected

Which versions of Angular, Material, OS, browsers are affected?

Angular 2.1.2, MD-alpha.10, Chrome, FF

Is there anything else we should know?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions