md-input

[jelbourn]

Blocked on #84

[ekarlso]

Hi, is there any eta on this part?

[jelbourn]

@ekarlso it's in progress #161

[hansl]

Merged #161 . I'm going to close this and open issues for missing parts.

[fxck]

@hansl @jelbourn I can tell you about few

• no styles for invalid inputs
• there's an issue with using [value] instead of [ngModel], but that could be related to binding inputs with [value] + ngControl angular#7690
• no textareas
• no bottom margin, this is way too stacked on each other
  
• while I like that there's just one component, unlike ng1 which had wrapper <md-input-container>, it makes it less friendly for customisation, since you can't easily utilise the md-is-active css class

[jelbourn]

@fxck

• Invalid styles and textareas will be coming
• The lack of margins is an intentional, library-wide design decision. It should be up to the user of the components to set margins, not the authors.
• I'm not sure what you're referring to with md-is-active; I don't see a reference to this anywhere in the material1 source. Do you have some customization use-case in mind?

[fxck]

The lack of margins is an intentional, library-wide design decision. It should be up to the user of the components to set margins, not the authors.

Good to know, thanks! Although material1 used that free space to show errors, which seems reasonable.

I'm not sure what you're referring to with md-is-active; I don't see a reference to this anywhere in the material1 source. Do you have some customization use-case in mind?

Yea, sorry, I meant md-input-focused, basically I want this...

...which means my own "pseudo-label", and I want it to be blue when the input is focused, I haven't used material1 for ages, but think this was possible

<md-input-container>
  <h2 class="my-special-label">Whatever</h2>    
  <input ng-model="foo.bar">
</md-input-container>

.md-input-focused .my-special-label {
  color: whatever;
}

[jelbourn]

@fxck we could potentially add an isFocused property to the input. That would enable:

<md-input #nickname [class.pajama-party]="nickname.isFocused">

[fxck]

Yeah that's what I was thinking as well. That would sort of fixed the problem.

[hansl]

There is already, it’s called focused.

-- 
Hans Larsen
Sent with Airmail

On April 7, 2016 at 10:29:49 AM, Aleš ([email protected]) wrote:

Yeah that's what I was thinking as well. That would solve the problem.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

[fxck]

Hello there @jelbourn @hansl, are those textareas and error styles going to be part of alpha.3? Since that new issue for missing parts doesn't really exist yet, it's hard to guess. Thanks!

[jelbourn]

@fxck we haven't scheduled those features yet- the team is gearing up for ng-conf, so it will be some time after that.

[fxck]

I know I'm annoying, but is there ETA for textareas yet? I wonder by what method you decide which components have bigger priority than other, because to me, it would make sense to start with the basics, to which textarea arguably belongs, and then follow up with more fancy stuff, like md-bottom-nav..

[jelbourn]

@fxck No ETA yet; one of our 20% contributors will probably take this on after they're finished with their current stuff.

[AhsanAyaz]

+1 for the text area

[CoreyGrant]

Are there any plans on validation? And by that I mean error styles, and potentially even messages tied into reactive forms.

[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.}