Not that anyone ever made such a promise.
Specifically, I’m talking about DOM events. Take the HTML5 <canvas> element, for example. If I give
by popping up the device’s soft keyboard in response to the canvas element receiving focus (ie, when you tap on it).
The Silk browser on a Kindle Fire, however, is another story – it acts like it has no idea what
means. Even if I display an actual <input> text field alongside the <canvas>, and attach all the same
input event handlers to the text field instead of the canvas, the Kindle Fire’s soft keyboard will pop up, but my
input event handlers still won’t fire.
I’ve done what testing I can with the Android SDK and the “Android Virtual Device Manager”, and in general, support looks fine – you click/tap on the PC’s screen, the soft keyboard pops up, and typing works. So I guess Silk is just an outlier. I’m not sure what I’ll do about it yet (or even what I can do).
Here’s another issue I’ve yet to resolve.
It may be possible to work around the bug, but I haven’t yet isolated exactly what code sequence(s) are failing. For now, this is the most serious unresolved PCjs bug I’m aware of.
If you’re having a problem (or trouble with a device) that I’ve not already mentioned, let me know. Thanks.
March 31, 2014