input[type=number] doesn't respect the scientific notation

[stryju]

Hi.

just today, I came across a weird behavior - angular's input[type="number"] directive doesn't see scientific number notation (like 1e2) as a valid one, despite the fact, that browsers do.

is that on purpose?

[Narretz]

Do you mean when setting on the model or in the input?

[stryju]

input

---

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

type in the input 1e3

• :invalid selector does not apply
• native form validator say everything's OK
• angular form directive says otherwise

[stryju]

screenshots of failed validation - just to confirm that it works:

• 
• 

[RogerJFX]

Simply change angular.js as a workaround, until it is fixed. It works for me. By the way this might already be some kind of fix. Maybe a '+' is missing, if someone wants to write e.g. 1E+12

var NUMBER_REGEXP = /^\s*(\-|\+)?(\d+|(\d*(\.\d*)))([eE]+[-]?\d+)?\s*$/;

[Narretz]

@RogerJFX would you mind sending a PR with this change and a test for it?

[RogerJFX]

Ok, I can do this. Anyways one issue will remain. Current browsers can not interpret the step attribute of input[type="number"], if value is in scientific notation but not step and vice versa.
So anything like this

<input type="number" step="1" value="1e2" />

will not work as expected.
As far as I remember, all browsers fail here.

[stryju]

works in chrome - converts to "normal" notation tho

[Narretz]

fixed in ebd0fbb

[zvuv]

the trick seems to be to add the decimal point. 1.0e-7 seems to work on most browsers