Open mikehearn opened 4 years ago
I realised that the device in question was really struggling with WiFi. The connection had some bad latency and packet loss. The warning is still real but, I guess, it is expected that a remote desktop solution like JPro will suffer in times of bad connection latency.
Something that'd be good is if there was a way to get the browser to handle text input for TextField nodes. That way mobile browser selection widgets would work. Currently you get plain for-the-mouse desktop style text selection operations because the host manages it. For cases where you don't take much control over a TextField a browser-side edit would be sufficient, and would hide most latency, which is most painful when typing.
Text edits on Android often feel like they're lagging. I'm not sure this is a latency issue, in the logs I see a lot of messages like
Unknown Keycode: 229
And from Googling this warning it seems that 229 is some magic keycode that is related to soft keyboards, which has confused other web devs in the past. It might be worth investigating.