Hey Adam,
The lag is horrible on the simulator and slightly less horrible on the real device. Still it's definitely there and people notice it. My app has very few event listeners but yet it manages to act quite laggy. Recently when I added sound this lag got amplified. When the user types somewhat fast (not ridiculously fast, just doable fast) the audio can't keep up with the keypresses which results in a pretty crappy experience. I wanted to add audio feedback to keypresses and expected it to be just as snappy as the built in keyboard. It's far from it.
Note that I have seen this exact same problem on Palm WebOS. The Palm solution to it was to offer a special API call that would play a sound from a limited set of predefined system sounds. For the PlayBook it would be awesome if there was such a call that would play the same sound you hear when using the regular keyboard on the PlayBook. This system call that Palm provided allowed me to have lag-free audio feedback when pressing keys.
Anyway, as you understand from this, it's not really a defect. It's just something that's a bit crappy in just about any browser, even desktop ones. So I suppose my request is more of a feature request rather than a bug/defect report.
So, ideally there would be some call in the WebWorks API that plays a system sound with 'top priority' when called. This would enormously enhance user experience in many apps that have their own on-screen keyboard.
