Missing Period/Dot on android virtual Keyboard

[Jorge Bonafé]

I tried the demo with two different phones. When editing the number input, the period/dot won't show on the edit field when the period is clicked on the virtual keyboard. And although it won't show on the edit field, when I finish typing and enter, it shows on the block as it should. It is very confusing... I couldn't find a solution to this. Does anyone know if there is a way to fix this? I've uploaded a couple of photos to show what I mean.

[Andrew n marshall]

Hey Jorge,

This is new to me. I'm using a Nexus 6P, and it's default Google keyboard. When editing the math_number block in the Blockly Simple demo, I see the decimal point just fine.

Your screenshot implies a very different virtual keyboard. Unlike your screenshot, my edits are shown in place, not occluded my the virtual keyboard. What devices and versions of Android did you try?

On Aug 29, 2016 18:38, "Jorge Bonafé" <jorge...@gmail.com> wrote:

I tried the demo with two different phones. When editing the number input, the period/dot won't show on the edit field when the period is clicked on the virtual keyboard. And although it won't show on the edit field, when I finish typing and enter, it shows on the block as it should. It is very confusing... I couldn't find a solution to this. Does anyone know if there is a way to fix this? I've uploaded a couple of photos to show what I mean.

--
You received this message because you are subscribed to the Google Groups "Blockly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blockly+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jorge Bonafé]

One is a Samsung gt i9300 with android 4.3, and the other is a Motorola razr i with android 4.4.2.

I was messing with the language settings on my phones, and I noticed a setting, "android keyboard aosp" on the motorola and "Samsung keyboard" on the samsung. When disabled on both, they started working as you said, shown in place, and the decimal showed fine.

I'm not sure why this setting messed up the input, but it's now working in any case. Thank you for the quick response. Maybe knowing this setting has issues will be useful for the development of the api, I guess :P

[Andrew n marshall]

It's definitely good to know other virtual keyboards aren't behaving as expected. I will file a bug to track this, but probably won't investigate until we see more reports.

Thanks for letting us know!

--