Fix TextField parse functionality

[manuelmeister]

I've corrected the way we handle numbers in our e-textfield and api-textfield. Currently this transformation is done at the wrong place. For v-model we can use the .number modifier to get a number. For the api-textfield I've implemented a parse function, that parses the value if attribute type="number" or inputmode="numeric" is set.

Currently in the MaterialTable it was not possible to have fraction numbers (1.2 kg Mehl). With this change it is now possible to input these values. On mobile the number keyboard is shown if you set inputmode="numeric".

[github-actions]

⛔ Feature branch deployment currently inactive.

If the PR is still open, you can add the deploy! label to this PR to trigger a feature branch deployment.

[BacLuc]

I've corrected the way we handle numbers in our e-textfield and api-textfield. Currently this transformation is done at the wrong place. For v-model we can use the .number modifier to get a number. For the api-textfield I've implemented a parse function, that parses the value if attribute type="number" or inputmode="numeric" is set.

Currently in the MaterialTable it was not possible to have fraction numbers (1.2 kg Mehl). With this change it is now possible to input these values. On mobile the number keyboard is shown if you set inputmode="numeric".

I cannot reproduce your bug.
On dev it was no problem to use fraction numbers.
https://dev.ecamp3.ch/camps/6973c230d6b1/Harry-Potter-Lager/material
I used "." for the English way to create fraction numbers, and "," for the german way.

[manuelmeister]

In Chrome on the Mac, I have to enter the numbers with a comma, which doesn't make sense because I have set the region to Switzerland, so it should use the dot to indicate the decimal point. Just the problem on the Mac is poor UX for Swiss users.

On mobile Safari on iOS it is currently impossible to enter decimal numbers, which is really bad.

The number input type should only be used for incremental numbers, especially when spinbutton incrementing and decrementing are helpful to user experience.
Source: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/number#using_number_inputs

I think it is better to let users type in a field and and then show a parse error, than to just not "allow" decimal numbers for some users. (Because a Swiss user would never expect a decimal to be formatted with a comma)

Maybe in the future we can provide German parsing (with a comma) but until then, I would suggest we focus on our Swiss userbase.

[usu]

Desktop auto save doesn't work for me

[manuelmeister]

@usu can you test again? I could not reproduce your problem.

[usu]

@usu can you test again? I could not reproduce your problem.

Seems to work now. Couldn't reproduce either