Max height quest doesn't allow inputting two-digit height values

[waldyrious]

I'm not sure if this is a regression of #3000 or a new issue altogether, but I am again unable to enter large height values (10m or more). This time it's not due to a limitation in the total number of characters (as was the case in #3000), but rather due to only being able to input a single digit before the decimal point.

Here's a screen recording of me hitting this limitation:

output8.mp4

[waldyrious]

For additional context: Here in Portugal, it is quite common, at least in the North, to have extremely high "clearances" under highway bridges simply due to the geography of the terrain. Here are two notes I left due to being unable to enter the correct values in the app: 3865957, 3865958. For illustration here's a Mapillary shot corresponding to the first note.

[matkoniecz]

For illustration here's a Mapillary shot corresponding to the first note.

Is there a height limit sign there?

[waldyrious]

Is there a height limit sign there?

Yes, of course — I couldn't obtain the height otherwise. It's here:

Thanks for the quick fix, @westnordost!

[matkoniecz]

Yes, of course — I couldn't obtain the height otherwise. It's here:

Oh, I completely missed it (even when pointed out on photo I cannot really read it). Thanks, that makes sense to me now!

[waldyrious]

even when pointed out on photo I cannot really read it

Yeah, I can't read it from the photo either :) but that was just an old image I found to illustrate the situation. I surveyed the info directly as a passenger in a recent car trip that passed under that bridge.

[waldyrious]

For the record, there were a couple ways I added an incorrect maxheight to before I noticed this bug, in changeset https://www.openstreetmap.org/changeset/140555809. Fortunately someone alerted me to the implausible maxheights, and I removed them in https://www.openstreetmap.org/changeset/142592971.