mdMaxlength: Always invalid for input type="number"

[aaronPMorabito]

An input flagged with type="number" and md-maxlength="#" will always have a validation error.

Can be seen in this example under 'Errors': https://material.angularjs.org/latest/demo/input

Material Design v 1.0.0-rc1

[topherfangio]

For clarification, the hourly rate input in the linked demo will always be invalid.

[topherfangio]

@aaronPMorabito We are talking about whether or not md-maxlength is meaningful on a number input. Can you provide some feedback as to how you are using this?

We are planning to update the demo to not use md-maxlength on the Hourly Rate input to cause less confusion.

[EladBezalel]

@topherfangio is this fixed?

[topherfangio]

@EladBezalel This is partially fixed, we have removed the md-maxlength attribute from the demo so as not to cause confusion, but we still need to talk about whether or not it makes any sense for number inputs.

Was hoping to get some more feedback from @aaronPMorabito on how it might be used to see if we want to support it.

I say we close it for now and we can reopen if we get more feedback unless @ThomasBurleson gave it a P1 for a different reason.

[aaronPMorabito]

@topherfangio I was only using it since it was in the demo and I thought it was fancy. I noticed that it was always causing validation errors when used in combination with type="number" so I reported it. I was using it to display the length of the string input and the max possible length of that string.

[bitbytebot]

We are talking about whether or not md-maxlength is meaningful on a number input.

Why would you exclude such a function specifically for <input type="number">??? It does make sense and I actually need it in my projects.

You force me and many others to use <input type="tel"> because of your exclusion.

[topherfangio]

@bitbytebot We haven't specifically excluded this, it's just that based on the feedback above, we didn't see it as a high priority bug since we didn't see a good use-case.

If you have a valid use-case, please do share and we can discuss reopening it.

Also, is <input type="tel" /> a good workaround, or does it cause problems?

Thanks!

[bitbytebot]

@topherfangio I have a use for it, but now I'm using <input type="tel" /> because it works similar to what I need.

I built a configurator for vehicle registration plates which have a maximum amount of number combinations (3). So this is a needed component, for me at least. I can think of multiple use-cases for this:

• zip code
• flight number
• vehicle identification number
• bank account number (IBAN in the SEPA-zone)

I could think of couple more. But there is definitely a use for it.

[Gaurav9969351313]

not working mdinput in IE10
type=number side arrow event

<input mdInput type="number" onkeypress="return event.code !='NumpadDecimal' && event.code!='Period'" [step]="10" [max]="100" [min]="0">

in chrome m getting the desired output as we press up down arrows it inputfield text jumps to 10 ( as step is=10 )

but same is not working in IE10 and IE11. kindly suggest the resolve the same.

do i need to update my polyfills...
if yes then please suggest for the same....
Thank You in Advance...:)