Input-container does not have an hidden property, and does not honor inner input hidden property

Bug, feature request, or proposal:

Right now there is no way to hide an input property, cause the input-container does not have (or does not honor) a hidden property. Also, it’s a hidden property it’s set in the input child, the input will hide, but the other “decorators”, placeholders, prefix, suffix, will not.

What is the expected behavior?

A way to actually hide a input.

What is the current behavior?

The input it’s not hided.

What are the steps to reproduce?

  <md-input-container
    fxFlex
    class="flex-item"
    *ngFor="let input of inputFieldList"
    hidden="true"
  >
    <input md-input
      [placeholder]="input.placeholder"
      [formControlName]="input.name"
    >
    </textarea>
  </md-input-container>

I tried also [hidden]="'true'" and [hidden]="item.hidden". Neither of them work.

If is set in the input, just the input gets hidden.

  <md-input-container
    fxFlex
    class="flex-item"
    *ngFor="let input of inputFieldList"
  >
    <input md-input
      [placeholder]="input.placeholder"
      [formControlName]="input.name"
      hidden="true"
    >
    </textarea>
  </md-input-container>

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

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

Angular 2.4.2 Material 2.0.0-beta.1

Is there anything else we should know?

I try to search, and did not find anything. Sorry if this is duplicated.

[crisbeto]

In general, we try to avoid defining global styles like this one, so I doubt that we’d add it to Material itself. I recommend either adding this to your CSS or using a class for hiding stuff.

[michaeljota]

But, I mean, I think the component should handle the display for itself, shouldn’t it? I know the hidden property it’s something built-in browsers, but still, a expected behavior if it is set to false, it’s for the component to hide, and the component should do it. I understand you mean, but you won’t, and it should not, override any built-in property, it just have to set it temporally as is, to be handle by the browser.