Allow Float values in height input box

[jguthrie100]

Fixes #5184
Seems to be as simple as switching the parseInt to parseFloat when parsing input values.

Only issue is that it allows float values for all tags set using the input box (i.e. 'motorway lanes', which should presumeably just be an integer! Not sure how to avoid this though, without doing something like type=integer or type=float in the tag presets json files

[bhousel]

Thanks @jguthrie100 !

Only issue is that it allows float values for all tags set using the input box (i.e. 'motorway lanes', which should presumeably just be an integer! Not sure how to avoid this though, without doing something like type=integer or type=float in the tag presets json files

Yeah, I thought about adding a dedicated integer field for fields that should be one, but I worry that many of the tags that we think of as integers also need to support text entry like no or yes, because this is an established OpenStreetMap convention.