MdSelect inside disabled fieldset should be disabled

[vincentpalita]

Bug, feature request, or proposal:

Bug

What is the expected behavior?

A md-select element should be disabled if it is inside a disabled fieldset like other fields such as input, textarea, ...

What is the current behavior?

You can use the md-select component even if its parent fieldset is disabled.

What are the steps to reproduce?

http://plnkr.co/edit/bXjtAGhH2jpM4jrSB3Pg?p=preview

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

When you wish to disable a full form it is very convenient to use a disabled fieldset. It will in fact disable everything and removes the need to disable each single field one by one.

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

Angular : "@angular/core": "4.1.3",
Material : "@angular/material": "2.0.0-beta.5",
Typescript : "typescript": "^2.3.3"

OS: OSX & Windows
Browsers : All

Is there anything else we should know?

None that I know of!

[tinayuangao]

Related to #2763

[crisbeto]

Should be resolved by #4334.

[Splaktar]

Seems to be tracked in angular/angular#13856.

[un1c0rnr1d3r]

Will this be resolved by angular/angular#13856?

The Material Select component is different than the other form control components because it does not render an actual <select> element. I think we'll need to add support for this in the Material library itself.

[thw0rted]

I think all related issues have been funneled towards angular/angular#35309 -- do I understand correctly that resolving that will fix this as well?

[jelbourn]

Closing this since the underlying issue is tracked on angular/angular#35309

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}