[SOLVED] No on-screen keyboard on the 7-inch local display?

[Nutul]

@Nutul

Finally got time to build your OSK on moOde 8.2.0.

Seems to work as advertised on my local touchscreen. It does obscure the bottom portion of the screen but have been able to scroll the moOde page(s) behind it so I could see the box I'm trying to fill. Don't know (yet) if there's any moOde-input box so low on a page that I can't see what I"m typing.

First time I tried it on my Pixel 3A phone, your OSK keyboard was stuck above the Android virtual keyboard but I think that's because I hadn't refreshed the browser since this hasn't recurred. FYI, if I rotate the phone to landscape mode while the OSK is up, I get a horribly elongated keyboard. Not so if I open it in landscape mode. (Just an observation, not a big issue IMHO.)

Seems well-behaved on my 9.7-in iPad 2017.

ETA - The above not withstanding, I hope you can figure out how to avoid it appearing on a remote device.

Candidly, I use the local touchscreen just for display and drive the player variously from phone, tablet, or laptop so the OSK is not an essential feature for me. Having said that, I think you've got a good thing going here.

Regards,
Kent

Hi Kent,

first of all, thank you for your time.

Then:

1. I am now able to run the OSK _ONLY_ on the local UI (unless you have an ARM based portable phone/tablet which can report the same navigator.userAgent string...), so no more weird overlapping/stretched keyboards.

2. maybe I have done some improvements since I uploaded the code for you to test:
2.1. not the OSK attaches to _ANY_ input with type="text"/"number"/"password"
2.2. while active, it extends the height of the container of the input fields by an amount equal to the OSK height, in order to be able to see even the bottom-most input. It restores the original container height on exit.

I am now dealing with the type="number" inputs, in order to be able to provide "bigger" and "easier" to access +/- buttons (they are so small, even on my laptop... imagine on the 7" screen)

TTYTT, I wasn't expecting it to appear everywhere... then I realized that the header.php is part of each and every UI context, hence automagically the keyboard was available on every configuration page.

I am happy enough that I was able to restrict it to the locally running Chromium, so that the graphic behavior won't affect any user controlling moOde by their phone/tablet/PC/laptop.

Hopefully I had every possible western character covered (at least all those needed for son titles AND/OR configuration strings).
Since I do have some Bulgarian/Russian artists in my library, rather than experimenting with transliteration/phonetization (which I have done in the past, and it's far from being easy), I believe I'll add just another keyboard layout to cover the cyrillic alphabet.

Maybe later tonight I'll be able to give you a release-candidate to check out... Then you'll adorably talk to @Tim Curtis, explaining him that the OSK is working wonderfully, it's not a resource/CPU hungry thing, and can be integrated, possibly, in the upcoming 8.2.1 release... :-D

Thanks again for your time.

Cheers, Al.