Need to ensure number validator works with i18n pattern

[cebe]

What steps will reproduce the problem?

Common use case is that Number inputs allow . and , but it could also be possible to allow formatted input like 1.024,56 which should be float 1024.56 in the end.

What is the expected result?

It is currently not documented how to do that, also unit tests are not covering such use cases.

What do you get instead?

Needs to be documented and tested.

I'm working on it.

[samdark]

Moved to 1.1.0 since it's not required for initial release. If you'll finish before 1.0.0, we'll move it back.